Assign automatic module names to core Maven components

[dmlloyd]

New feature, improvement proposal

Various Maven core artifacts are consumed by downstream projects (e.g. Quarkus). These downstream projects may be employing the Java platform's module system (colloquially known as JPMS). The lack of established automatic module names for Maven core components may cause some difficulty for these projects.

Each published artifact should include an automatic module name in its manifest. The automatic module name for each artifact should ideally be derived from the top-level package name of the classes within it.

This change should not impact compatibility in any meaningful way. It would be great to get this in 3.x as well as 4.x.

[cstamas]

@gnodet @desruisseaux

I know we have some overlapping packages (in Maven 3), unsure what is the state in Maven 4 (my fear, same IF those are in some compat modules)...