[
https://issues.apache.org/jira/browse/MPLUGIN-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733756#comment-16733756
]
Gili commented on MPLUGIN-341:
------------------------------
Guys, this is becoming more and more of a problem. If you take a look at
MJAVADOC-555 and MJAVADOC-561 you will notice that Oracle is slowly making it
impossible to mix named and unnamed modules. These limitations are by design
and won't be going away anytime soon.
I might have a workaround for MJAVADOC-555 (albeit a very annoying one) but as
far as I can see MJAVADOC-561 is a dead end. As of JDK 11 it has become
effectively become impossible to generate Javadoc for Maven plugins that depend
on named modules.
> 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
> Priority: Minor
>
> 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)
