Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorThomas Watson2019-11-14 12:01:29 -0500
committerThomas Watson2019-11-14 12:01:29 -0500
commita731195ec06070c34a03d7bfd15b51bfd1fd5283 (patch)
treecf2c8702d13f2bb5b81d274bb1bc9297f0c04f42 /launcher-binary-parent
parentb11a6c0a6552bd7152e6b25bc0c3b6fe7b912635 (diff)
downloadrt.equinox.framework-master.tar.gz
rt.equinox.framework-master.tar.xz
rt.equinox.framework-master.zip
Bug 552594 - Fix framework extensions with built-in Java 9 app loaderHEADI20191116-1800I20191116-0600I20191115-1800I20191114-1800master
In Java 9 the application class loader changed from a URLClassLoader to an internal type jdk.internal.loader.ClassLoaders.AppClassLoader. The new AppClassLoader no longer has the addURL method that we used to add framework extension content to the class loader when the framework is loaded from the java class path. This fix uses the method appendToClassPathForInstrumentation(String) on the new AppClassLoader class. To do this extra work is needed to allow reflection on the AppClassLoader class. This is not ideal, but will allow the framework extensions to work when the framework is launched from the java application class path. Note that Eclipse launcher uses its own class loader which still has addURL method available. This new approach is only attempted if the class loader used to launch the framework does not have an available addURL method. Change-Id: I0a4195307db6fb87dbab08933584e1a798ccf34a Signed-off-by: Thomas Watson <tjwatson@us.ibm.com>
Diffstat (limited to 'launcher-binary-parent')
0 files changed, 0 insertions, 0 deletions

Back to the top