Licensing Issues

[Alan Ruttenberg]

It is my understanding, as well, that the Classpath exception allows any
use of ABCL as a library, as long as ABCL itself is not changed - i.e. the
distributed JAR is not changed. An issue would arise if you want to change
one of the system functions and modified the original to do so. However in
that case it would better to simply submit the patch to the list. Also note
that if you are using GPL code completely privately, i.e. not
redistributing it, then you can have your way with it.

Note IANAL, but have some experience working with licenses.

Regards,
Alan

On Tue, Jun 30, 2015 at 2:24 PM Hamda Binte Ajmal <
hamda.binte.ajmal at gmail.com> wrote:

> Mark Evenson <evenson at ...> writes:
>
> > Thank you for your response.
> One more thing I would like to ask is that, I am using ABCL in a java
> project that is GNU GPL licensed.
> ABCL is not modified, just used as a library, and for executing lisp
> commands from Java project
> Such that
>         JAVA PROJECT (GNU GPL) -> ABCL (GNU with classpath exception) ->
> Lisp code
>
> Now my question is, would the GNU GPL license of Java project enforce
> GNU GPL on ABCL too which can enforce GNU GPL on my lisp code ?
> >
> > > On Jun 30, 2015, at 12:20, Hamda Binte Ajmal
> > <hamda.binte.ajmal at ...> wrote:
> > >
> > > Hello,
> > > I am using ABCL to run lisp files in my Java code.
> > > ABCL is covered by the GNU General Public License with Classpath
> > > exception, meaning that you can use ABCL in your application without
> the
> > > requirement to open the sources to your application. So, I conclude
> the
> > > GNU GPL is not going to effect the license of my Java Code,
> > >
> > > BUT, what about the lisp code I load using ABCL? Would it have to be
> > > released under GNU GPL ?
> >
> > No, Lisp code running on ABCL does not need to be released under the
> GPL.  The
> > licensing for ABCL applies to derivative works, i.e. modifying ABCL
> itself, not
> > Common Lisp code executing on ABCL.
> >
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/armedbear-devel/attachments/20150630/373afae9/attachment-0001.html>