fix for #13760 - running script compiled jar no longer restricted to java.base module #15103
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This resolves the problem described in #13760.
The essence of the problem: running a script with the
-save
option will throw aClassNotFoundException
, but only when running from the compiled jar, and only if the script references modules other thanjava.base
. The jar is fine when run viajava -jar <jarfile>
, the issue only occurs when scala launches the jar.The workaround for the problem has been to append the
-nosave
option to the hashbang line.The cause of the problem is that
bootClassLoader
in ScalaClassLoader is set tonull
when running injdk9+
.The following command line illustrates the problem code at
ScalaClassLoader line 70
:An explanation of why this code no longer works for
jdk9+
is described here: Regression in behavior of a null parent ClassLoaderThe proposed fix is based on the fix to #11658.