Rhino build support

Mark Wielaard mark at klomp.org
Wed Oct 19 08:28:33 UTC 2011

On Tue, 2011-10-18 at 20:10 +0200, Henri Gomez wrote:
> Mark (Wielaard)
> "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 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) ?

Yes, but that is what I am trying to prevent from happening :)
Note that IcedTea doesn't really "ship" Rhino itself. But it has
configure and build infrastructure to detect the system installed copy
of Rhino and transforms that so that it is available as separate module
under jre/lib.

IMHO if a JDK includes javax.script javascript support we should make
sure they include the same version and features. So we should try to
collect all versions/derivitives of Rhino being used with
OpenJDK/IcedTea/ClosedJDK and setup a canonical version (ideally just as
a branch of upstream Rhino). That would prevent subtle compatibility

I haven't been able to find the source code for the Rhino variant
shipped with the Oracle ClosedJDK. Since it is distributed under the
GPL/MPL, I assume the source code is somewhere for users to use, but I
might have missed where. Someone from Oracle (Mark R.?) might know where
the sources can be fetched from.



More information about the discuss mailing list