On 27/02/2017 13:45, Stephen Colebourne wrote:
:
Note here that as a general rule, it is always possible to refactor a
module into a number of single-package modules. (I can't actually
prove this offhand, but it seems an entirely reasonable claim).
Yes, assuming no cycles.
:
With regards to automatic modules, this implies that automatic modules
must contain the Module-Name MANIFEST information (as it takes too
long to scan a jar for packages).
The contents of JAR files containing automatic modules need to be
scanned anyway in order to determine the packages in the module, the
module name doesn't help.
:
In summary, module naming must match package naming, because modules
are ultimately just a collection of packages with
Some module don't contain any types/packages. Aggregator modules is one
example (`java.se` and `java.se.ee`). Resource bundles (for
i18n/translation) might only contain .properties files. Then there are
modules that only contain native code, one example in the JDK
is`jdk.jdwp.agent` (debugger agent).
-Alan
