JShell: packages

Alan Bateman Alan.Bateman at oracle.com
Fri Sep 18 13:03:09 UTC 2015



On 18/09/2015 13:49, Maurizio Cimadamore wrote:
> Adding Alan
>
> On 18/09/15 13:48, Maurizio Cimadamore wrote:
>> I had a productive chat with Alan - there's no bug here. The problem 
>> is caused by the fact that when you use bootclasspath, you force 
>> jshell to be loaded by the bootloader and, unfortunately, both jline 
>> and jdi are NOT in the bootloader (they are on the app loader); since 
>> bootclassloader doesn't delegate, you then get errors. As I 
>> understand, there's an hack to make this sort of things work with the 
>> exploded build, but it's just an accident that things work there.
Just to add to the point about why this works with exploded builds ...

With exploded builds then all types in all modules are defined to the 
boot loader. This is temporary but consistent with how exploded have 
always worked. It's completely replaced in the jake forest so that 
modules are defined to their appropriate loader irrespective of whether 
it's an exploded/developer or images build. Also the -Xoverride option 
in jake is independent of class loader and so can be used to override 
classes in any module (not just modules defined to the boot loader).

-Alan



More information about the kulla-dev mailing list