2011/10/17 10:06 -0700, henri.go...@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.
Thanks Mark
OpenJDK is GPL
Rhino is MPL
But when Oracle provide its JDK, you include both of them.
Which licence should be used by OpenJDK 'packagers/bundlers' so ?
On Tue, 2011-10-18 at 09:22 -0700, mark.reinh...@oracle.com wrote:
> 2011/10/17 10:06 -0700, henri.go...@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
> I suggest you ask a lawyer.
Thanks for the suggestion but individuals like me don't have lawyers
available so easily, especially those involved in licences issues :)
Usually there is people very aware of licences problematics in OSS
community, that's why I'm trying to get answers here :)
In Ic
Mark (Wielaard)
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
in general."
Do
Thanks Martijn
BTW, if Rhino should be bundled at higher level (i.e.: trunk), this
license discussion should be raised to upper level isn't it ?
2011/10/18 Martijn Verburg :
> Hi Henri,
>
> The EFF would also be a good place to ask and I'm working on trying to
> get some reasonably priced advice
On 20:08 Tue 18 Oct , Henri Gomez wrote:
> > I suggest you ask a lawyer.
>
> Thanks for the suggestion but individuals like me don't have lawyers
> available so easily, especially those involved in licences issues :)
>
> Usually there is people very aware of licences problematics in OSS
> com
One downside of not including it is that when you run "jrunscript" you get:
$ git develop* → jrunscript
script engine for language js can not be found
Jrunscript by default looks for a "js" engine and fails. Unfortunately, we
can't just take the latest Rhino from mozilla and put it on the clas
