Auto-modules vs. the unnamed module

Ceki Gulcu ceki at
Thu Apr 27 16:12:32 UTC 2017

On 27-Apr-17 5:22 PM, Alan Bateman wrote:
> The advantage of automatic modules is that it allows you to treat a
> library as a module when compiling or running. It essentially allows you
> to make progress on modularization without waiting for everything that
> you transitively depend on to migrate first.
> The State of the Module System document [1] needs a few updates but it
> still provides a useful introducing to the topic.

Quoting directly from [1]

   3.1 The unnamed module

   If a request is made to load a type whose package is not
   defined in any known module then the module system will attempt
   to load it from the class path.

Is the above statement true?

If it is, then there is no need for auto-modules for migrating 
piecemeal, placing a non-modular artifact on the class path should be 
sufficient to make its contents visible.

Ceki Gülcü


More information about the jigsaw-dev mailing list