Lukas Eder created MPLUGIN-341:
----------------------------------
Summary: Make the plugin tool modular or at least module-ready
Key: MPLUGIN-341
URL: https://issues.apache.org/jira/browse/MPLUGIN-341
Project: Maven Plugin Tools
Issue Type: Improvement
Affects Versions: 3.5.2
Reporter: Lukas Eder
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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
