Paul Fisher wrote:
>
> The FSF and Cygnus have agreed, in principle, to merge the libgcj and
> Classpath projects together.
This is great news! This should really speed up development of both
projects :)
> 1. libgcj and Classpath will both change licensing terms to the GPL
> with the following exception:
>
> /* As a special exception, if you link this library with other files
> to produce an executable, this library does not by itself cause
> the resulting executable to be covered by the GNU General Public
> License. This exception does not however invalidate any other
> reasons why the executable file might be covered by the GNU
> General Public License. */
A couple of points I made before but I didn't see a definite answer to -
I just want to make sure that they are dealt with:
Mozilla - according to Chris, Japhar runs *in-process* in mozilla, so
it's important that this new license isn't incompatible with the NPL. I
don't see why it would be, but I'm just checking...
Japhar - the use of the term "executable" in the above license seems to
exclude linking Classpath with Japhar to produce a *library* for adding
java support to a program. Since this is what Japhar does and it is
licensed under the LGPL for that reason (all Japhar *executables* are
licensed under the GPL already), I'd be interested to know how this
would work.
(one solution that occurs to me is dual-licensing like Perl, under the
modified-GPL and the LGPL... both licenses seem to exclude some uses,
but between the two of them all cases are probably covered)
Stuart.
