The boot classloader used to be sun.misc.Launcher, but it has been renamed. This may impact any code that walks the classloader tree with the assumption that sun.misc.Launcher exists.
This will definitely cause any project that uses a dynapath less than 0.2.4 to fail to load, since it made that assumption. And any project that uses dynapath less than 0.2.5 may fail under Java 9 when AOT'd, and will get an exception when trying to modify a URLClassLoader as of Java 9-ea+148.
The app classloader is no longer a URLClassLoader, so any code that assumes it is will fail.
These dynapath issues affect:
The app classloader changes affect:
The boot classloader used to be
sun.misc.Launcher, but it has been renamed. This may impact any code that walks the classloader tree with the assumption thatsun.misc.Launcherexists.This will definitely cause any project that uses a dynapath less than
0.2.4to fail to load, since it made that assumption. And any project that uses dynapath less than0.2.5may fail under Java 9 when AOT'd, and will get an exception when trying to modify aURLClassLoaderas of Java 9-ea+148.The app classloader is no longer a
URLClassLoader, so any code that assumes it is will fail.These dynapath issues affect:
The app classloader changes affect: