Assign automatic module names to core Maven components
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
### 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.
Contributor guide
Assessment
This issue has not been assessed yet.