[MPLUGIN-341] Make the plugin tool modular or at least module-ready

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 3.5.2
• Assignee: Unassigned
• Reporter: Lukas Eder
• Created: 15/Jun/18 14:44
• Updated: 04/Jan/19 09:52

Description

When implementing custom maven modules, it is currently not possible to make those plugins modular on JDK 9+. The reason for this is that there are a lot of split packages among the various libraries, such as the org.apache.maven.plugin package between:

• org.apache.maven:maven-core:3.5.3
• org.apache.maven:maven-plugin-api:3.5.3

This, and the fact that there are not Automatic-Module-Name entries in the manifests (see http://branchandbound.net/blog/java/2017/12/automatic-module-name/), means that no one can currently reasonably create modular maven plugins.

It would be cool if these two things could be fixed in the next minor or major release

Issue Links

• blocks: MJAVADOC-561 Not possible to link to JDK classes since Java 11
• blocks: MJAVADOC-555 Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java