Refactor Maven Core to Full Java Modules
Original Item: "Refactor all Maven Core parts and dependencies to full JPMS modules (if not possible for a dependency, at least automatic module is a must) (Hendrik)"
Problem Statement
While we add more and more support for Java modules to the functionality of Maven, the project itself stays a non-modular-source project.
Current State / Starting Point
Maven Core is not itself based on Java modules (modular-sources). Some dependencies are explicit Java modules, some work as automatic modules, and some cannot be used on the module path at all due to Java module violations, e.g., split packages.
Expected Outcomes / Benefits
We should move Maven forward and refactor it to become based on Java modules that can use respective benefits (like access restrictions). This will end in a better modularization of Maven and better support for JPMS-based projects. All dependencies should be Java modules. Here we will contribute to those dependencies that are not yet Java modules.
Final Discussion (2026-02-24)
- Discussion:
- Must not start before Maven 4 GA
- Step-by-step implementation in close coordination with the Maven community
- Decision: Request Funding