Re: [equinox-dev] Eclipse won't work on JDK9b61 unless default classloader hiearchy is changed

2015-05-12 Thread Daniel Megert
As of http://download.eclipse.org/eclipse/downloads/drops4/I20150511-2130/ Eclipse starts again using the latest JRE 9. Dani From: Tom Schindl tom.schi...@bestsolution.at To: equinox-dev@eclipse.org Date: 07.05.2015 22:23 Subject:Re: [equinox-dev] Eclipse won't work

Re: [equinox-dev] Eclipse won't work on JDK9b61 unless default classloader hiearchy is changed

2015-05-07 Thread Tom Schindl
-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

Re: [equinox-dev] Eclipse won't work on JDK9b61 unless default classloader hiearchy is changed

2015-05-07 Thread Tom Schindl
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

Re: [equinox-dev] Eclipse won't work on JDK9b61 unless default classloader hiearchy is changed

2015-05-07 Thread Thomas Watson
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

Re: [equinox-dev] Eclipse won't work on JDK9b61 unless default classloader hiearchy is changed

2015-05-07 Thread Tom Schindl
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;

Re: [equinox-dev] Eclipse won't work on JDK9b61 unless default classloader hiearchy is changed

2015-05-05 Thread Thomas Watson
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? I still believe the default 'parent' class loader for bundles should be 'boot', but the class loader used to load up the