Adding boot and platform module flags to ResolvedModule

[Alan Bateman]

On 06/10/2016 17:15, Scott Stark wrote:

> Hello,
>
> I'm currently prototyping an alternate bootstrap implementation that will allow packages with the same name to exist across modules, and one thing I have run across is the need to know what the boot and platform modules are since there are restrictions on what type of ClassLoader can be used with them. Currently this information is located in the
> jdk.internal.module.ModuleLoaderMap class. In my prototype I just exposed that info via static public methods on ModuleLoaderMap, but it seems like the appropriate place for this is as read only attributes on the java.lang.module.ResolvedModule class.
>
> Does that make sense?
ModuleLoaderMap is generated at build time with the mapping of modules 
to loader. Once the VM initialized then there shouldn't be any further 
need for it and not clear that it would be worth exposing it in the API. 
Maybe you could expand a bit more on what you doing as it's hard to 
understand how you might use this.

-Alan