|
Bugzilla – Bug 213 |
JRuby Interpreter fails to start if any interpreter has been started beforehand |
Last modified: 2011-03-23 18:20:35 CDT |
| ⚠ |
NOTICE! This is a static HTML version of a legacy Fiji BugZilla bug. The Fiji project now uses GitHub Issues for issue tracking. Please file all new issues there. |
| JRuby Interpreter fails to start if any interpreter has been started beforehand | |
|
|
|
||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||
I _think_ that this has nothing to do with a previously invoked interpreter, but rather something with the way ImageJ handles updates: a new classloader is instantiated, and we require that to be a FijiClassLoader (because ImageJ's PluginClassLoader has no idea about jars/). If I am correct, then IJ.getClassLoader() will return an instance of PluginClassLoader, not of FijiClassLoader. You can test this by running this little macro: eval("script", "IJ.log('' + IJ.getClassLoader());"); (This requires Java6, because earlier Java requires jars/js.jar, which is not found if the classloader is not a FijiClassLoader).