On 27 February 2017 at 20:44, Alan Bateman <alan.bate...@oracle.com> wrote: >> 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).
While interesting, these are edge cases. A developer can always add .xxx to a package name they control to get a name for the edge case. Stephen
