Sigh, bootclasspath again

[Jonathan Gibbons]

Weijun Wang wrote:
> Is there any workaround to this? Say, compile your several classes into another module which is nearer to core than core.jar itself?
>
> I often create a small jar and tell the customer to try it with -Xbootclasspath/p: before I finalize a fix.
>
> -- Max
>
> On Apr 7, 2010, at 10:01 AM, 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.
>>
>> -- Jon
>>     
>
>   

Max,

In legacy mode, -Xbootclasspath/p: is supposed to work, so if it doesn't 
work, that's a bug that needs to be fixed. In the new modules mode, you 
would be able to deliver a new copy of an updated module, which could 
either be installed in the system library, or you could install it by 
itself in a temporary library using the main library as the parent. You 
could then run your code with -L tempLib must as you would do 
-Xbootclasspath/p: now.

Eventually, it will all be much better. What you are seeing here on this 
-dev list is the pain of transitioning to that world, where we have code 
and tools that do not know about or use the new features yet, and worse, 
code and tools which needs to be somewhat bimodal for the time being.

-- Jon