Sigh, bootclasspath again
jonathan.gibbons at oracle.com
Tue Apr 6 19:35:52 PDT 2010
Mandy Chung wrote:
> Jonathan Gibbons wrote:
>> Jonathan Gibbons wrote:
>>> Is -Xbootclasspath/p: supported in JVM legacy mode?
>>> I'm beginning to suspect it is not. Can anyone confirm one way or
>>> the other?
>>> -- Jon
>> I have proof that it is not, for those that want to wade through the
>> debugging output from my test. This is a big deal bug.
> -Xbootclasspath/p: is expected to work in JVM legacy mode as it is.
> In JVM legacy mode, the launcher sets -Xbootclasspath/p:<list of all
> modules> and passes it to the VM. I set _JAVA_LAUNCHER_DEBUG
> environment variable and confirms that the user-specified
> -Xbootclasspath/p: and the -Xbootclasspath/p: computed by the launcher
> are passed to the JVM.
> The VM should be able to take one or more -Xbootclasspath/p options.
> I'll need to investigate further.
Thanks, I'll try using that _JAVA_LAUNCHER_DEBUG variable and see what
output I get.
From my tests, I saw that my environment worked (a test behaved as
expected) using a recent 1.7.0 build, but not with the latest Jigsaw
jdk-modules-image. Printing out the URL for javac's entry class and
printing sun.boot.class.path seemed to indicate -Xbootclasspath was not
More information about the jigsaw-dev