Re: [Jython-dev] Licensing Question

[<bc...@wo...>]

[Brian McCallister]

>I am in the process of exploring embedded scripting options for a 
>large commercial application (written in Java) and was wondering 
>what the licensing restrictions for embedding the Jython runtime 
>interprter are.
>
>I have no desire (professional, not personal - personally I would 
>love to hack Jython) to extend the interpreter, just embed it as 
>is.
>
>I could not find any detailed information on mbedded licensing. 

There isn't any special treatment of embedded use.

>Looking 
>over the license information at http://www.jython.org/license.html 
>it would seem that we need to make the sourcecode available. 

What gives you that impression? If you make modification to the jython
source, you have to indicate the nature of the modifications. For
example:

   - bug fixed in jython
   - improved embedability of jython.

You could can write that right next to all the copyright lines that you
also have to show somewhere:

    Copyright (c) 2000, Jython Developers
    All rights reserved.

    Copyright (c) 2000 BeOpen.com.
    All Rights Reserved.

    Copyright (c) 2000 The Apache Software Foundation.  All rights
    reserved.

    Copyright (c) 1995-2000 Corporation for National Research
    Initiatives. All Rights Reserved.

    Copyright (c) 1991-1995 Stichting Mathematisch Centrum, Amsterdam.
    All Rights Reserved.

>It is 
>not immediately clear, but it seems to be, that the sourceode of 
>the program it is embedded in does not need to be made available.

It doesn't.

>Before I can make a proposal that we use Jython (which I would like 
>to do)I need to clear up the licensing issues. However, opening up 
>the entire application under the GPL (or compatible license) is not 
>an option.
>
>As the Jython developers, what is your read on the license (iow, 
>if you hold that it would require the whole application it is used 
>as an embedded interpreter within, then I will not bother to go talk 
>to the company lawyer). I do not consider anything you say to be 
>legal advice, and IANAL need not prefix any replies as I will not 
>pretend it does.

The licenses allows you to do almost everything except:

   - claiming that you wrote it
   - suing the authors.

<wink>

regards,
finn