Rhino build support
henri.gomez at gmail.com
Tue Oct 18 18:10:48 UTC 2011
in case of openjdk-osx-build there is about 0 closed source, since its
full build process is available on GoogleCode.
"Making sure all our work on Rhino, whether it is for ClosedJDK, OpenJDK,
IcedTea, or the bsd/macosx-port is done upstream seems like a good idea
Do you means, Rhino could be put back upstream ?
In the interim, do you think I could include it in my own builds (os/x port) ?
2011/10/18 Mark Wielaard <mark at klomp.org>:
> On Tue, 2011-10-18 at 09:22 -0700, mark.reinhold at oracle.com wrote:
>> 2011/10/17 10:06 -0700, henri.gomez at gmail.com:
>> > ...
>> > I couldn't find officials indications or documentation on how to add
>> > Rhino from Mozilla to OpenJDK build.
>> > Questions :
>> > 1) Did there is any reason why Rhino is not included in bsd-port (and
>> > so macosx-port) like licence problems ?
>> Yes, license problems. Rhino is licensed under the MPL,
>> which is fundamentally incompatible with the GPL.
> Rhino is available under the MPL/GPL dual license, so should be GPL
> compatible. And GPL+Exception should be compatible with MPL (if the MPL
> part is kept as a separate module). If that isn't enough for some
> people, we could see whether upstream wants Rhino to upgrade to MPLv2
> (which would add all secondary MPLv2 licenses too, so LGPL and AGPL dual
> licenses next to the current MPL/GPL) [*].
> I talked to Luis Villa and Gervase Markham about a possible upgrade and
> the implications. They have both worked on MPLv2 and were very
> supportive (but of course it will be up to the actual upstream Rhino
> developers to decide whether or not to upgrade).
> I think it would be really beneficial to make upstream, ClosedJDK,
> OpenJDK and IcedTea share the exact same version of Rhino. Currently
> IcedTea uses the (latest) upstream version available, but that might
> lead to subtle incompatibilities.
> But I couldn't find the actual Rhino source code used in ClosedJDK.
> Where is that currently available?
> Making sure all our work on Rhino, whether it is for ClosedJDK, OpenJDK,
> IcedTea, or the bsd/macosx-port is done upstream seems like a good idea
> in general.
More information about the discuss