Class names in java.lang.Module

Stephen Colebourne scolebourne at
Mon Sep 26 10:19:32 UTC 2016

Most coding only uses the simple name, not the fully qualified one,
and Configuration does occur in other projects [1].

The original poster referred to the package, where Configuration is
the only non-exception class that does not have "Module" in the name



On 26 September 2016 at 10:25, Neil Bartlett <njbartlett at> wrote:
> Module is already in the name: “java.lang.module.Configuration”. Wouldn’t “java.lang.module.ModuleConfiguration” look really odd?
> Neil
>> On 21 Sep 2016, at 16:18, Stephen Colebourne <scolebourne at> wrote:
>> I had the same thought while watching the slides. Configuration is
>> certainly a class name that exists other places, and would benefit
>> from being ModuleConfiguration. Layer is less common, so not worried
>> so much. Exceptions with "Module" in the name like
>> ModuleNotFoundException would also be clearer.
>> Stephen
>> On 21 September 2016 at 03:36, Kasper Nielsen <kasperni at> wrote:
>>> Hi,
>>> I was wondering if there are any reasons for why these 3 classes in
>>> java.lang.Module
>>> Configuration
>>> FindException
>>> ResolutionException
>>> Does not include the name Module?
>>> I especially am not to fond of the very generic Configuration name in my
>>> source code would much prefer something like ModuleConfiguration.
>>> Best
>>>  Kasper

More information about the jigsaw-dev mailing list