on JDK9b61 unless
default classloader hiearchy is changed
Sent by:equinox-dev-boun...@eclipse.org
Hi,
[...]
But you mention that using the boot class loader as the parent class
loader for bundle class loaders causes problems for Nashorn. I fail to
see why that is.
I don't know the inner
-dev@eclipse.org
Date:05.05.2015 16:06
Subject:Re: [equinox-dev] Eclipse won't work on JDK9b61 unless
default classloader hiearchy is changed
Sent by:equinox-dev-boun...@eclipse.org
Please
Hi,
On 05.05.15 16:05, Thomas Watson wrote:
Please open a bug to track the issues. I assume you are having to set
the configuration property osgi.frameworkParentClassloader=ext to get
this to work on Java 9?
Yes
I still believe the default 'parent' class loader for bundles should be
I think you miss-interpret what I am saying. The framework, Equinox or Felix have no control over what class loader is used to load the framework implementation. That is up to the launcher. Forever the Eclipse launcher has set the default parent class loader of the class loader used to load the
Hi,
[...]
But you mention that using the boot class loader as the parent class
loader for bundle class loaders causes problems for Nashorn. I fail to
see why that is.
I don't know the inner details but if you run this app
package samplenashornosgi;
import javax.script.ScriptEngine;
] Eclipse won't work on JDK9b61 unless
default classloader hiearchy is changed
Sent by:equinox-dev-boun...@eclipse.org
Hi,
Starting with b61 org.w3c.dom.** classes have been moved to
* app classpath in b61
* ext classpath in b62
Isn't it time to throw out this none standard class lookup
Hi,
Starting with b61 org.w3c.dom.** classes have been moved to
* app classpath in b61
* ext classpath in b62
Isn't it time to throw out this none standard class lookup strategy and
use at least ext.
https://bugs.openjdk.java.net/browse/JDK-8042244