Proposal: #CustomizableAutomaticModuleNameMapping

David M. Lloyd david.lloyd at
Thu Jun 30 11:30:07 UTC 2016

On 06/29/2016 07:03 PM, mark.reinhold at wrote:
> 2016/6/29 8:08:40 -0700, david.lloyd at
>> On 06/28/2016 04:23 PM, Mark Reinhold wrote:
>>> ...
>>> Proposal
>>> --------
>>> Extend the `java.lang.module.ModuleDescriptor.Builder` API so that it
>>> can be used to create automatic as well as explicit modules.  This will
>>> allow a container application to use a custom `ModuleFinder` to manage
>>> the mapping from artifact names to module names, version strings, and
>>> so forth.
>> Could you please clarify how, after this change, an automatic module
>> would be different from a regular module, from the perspective of any
>> code which is using the descriptor Builder API?
> The `isAutomatic()` method of an explicitly-built automatic
> `ModuleDescriptor` instance will return `true`.

Yeah, I get that, but I mean when looking at the final built module.  I 
assumed that to be implied since building the descriptor is useless if 
you don't make a module out of it.  Are automatic modules substantially 
different from regular modules in any way?  If not, is there a reason to 
continue to have them?


More information about the jpms-spec-observers mailing list