Licensing Issues

Alessio Stalla alessiostalla at gmail.com
Tue Jun 30 11:29:51 UTC 2015


As far as I know, it is called "Classpath" exception not because it only
applies to Java libraries, but because it was designed for GNU Classpath
(open implementation of Java's standard library). The wording of the
license doesn't say anything specific to Java; it only speaks about dynamic
linking, and as such, it applies to Lisp as well. At least, this is my
reading of it; I'm Not A Lawyer.

On Tue, Jun 30, 2015 at 12:20 PM, Hamda Binte Ajmal <
hamda.binte.ajmal at gmail.com> 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 ?
> Regards,
> Hamda
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/armedbear-devel/attachments/20150630/a36f6f2d/attachment.html>


More information about the armedbear-devel mailing list