ceylon/ceylon-spec — Issue #165: Revisit Module/Package model API for Java/Maven modules
Author: FroMage
Created: 2012-02-06 16:10:42+00:00
State: open
Labels: high priority, improvement, refactoring

Java and Maven don't have the same idea as Ceylon of what a module is.

For example, in Maven it's common to have modules that contain sub-packages (`a.b.c`) of other modules (`a.b`), not in Ceylon.

In Java it's worse because even the JDK contains several `javax` and `org.w3c` packages inside its module, and for Java 8 modules they plan on allowing module boundaries to cross mid-package: two modules contain different parts of a single package.

The current Java ClassLoader model allows for classpath entries to contain the same package (or parts of a package) in different modules (and indeed this is often the case that a package is split in parts, or simply duplicated in multiple jars).

What can the current model for `Module`/`Package` deal with that?