[Bug 179] javascript script support through rhino should not be on bootclasspath

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=179





------- Comment #6 from hannes at helma.at  2010-01-15 13:08 -------
Regarding my proposal in comment #2 of including the ScriptEngine
implementation in Rhino: I've done some work on this in Rhino using the code
from scripting.dev.java.net, but unfortunately ran into some erratic behaviour
when selecting scripting engines (see my last comment on that bug)

https://bugzilla.mozilla.org/show_bug.cgi?id=379385#c3

(In reply to comment #5)
> We don't want to be maintaining our own fork of Rhino within IcedTea.  I think
> we need to look at a solution whereby Rhino is loaded with a lower priority
> classloader that can be overridden.
> 
> An interim solution, other than the -Xbootclasspath setting suggested by Mark,
> would be to remove the symlink from the JDK install. 

Yes, this would be the best solution - if it is feasible, which I'm not sure
about. I would welcome any efforts in that direction from OpenJDK developers. I
tried hacking the OpenJDK scripting engine code myself at one time, but was a
bit overwhelmed by its build system (and build times).

I agree with Kohsuke that this is seriously hurting projects using their own
version of Rhino.


-- 
Configure bugmail: http://icedtea.classpath.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.