[
https://issues.apache.org/jira/browse/MNG-6516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16906578#comment-16906578
]
Giovanni Lovato commented on MNG-6516:
--------------------------------------
[~rfscholte] Does this mean one cannot adopt JPMS in his own plugin? I have
several plugins part of a Maven multi-module project which I'm porting to JPMS
and the JavaDoc plugin fails to produce aggregate docs if there's even just one
module not adopting JPMS.
> Build maven-mojo using Java9 fails
> ----------------------------------
>
> Key: MNG-6516
> URL: https://issues.apache.org/jira/browse/MNG-6516
> Project: Maven
> Issue Type: Bug
> Components: Plugin API
> Environment: java 9
> Reporter: Matthias Fuchs
> Assignee: Robert Scholte
> Priority: Major
> Labels: java9, modules
>
> I'm upgrading my Java8 framework to Java9, but I have major problems
> upgrading my mojos
> (https://github.com/spot-next/spot-framework/tree/develop/spot-maven-plugin).
> The problem is that my dependecies maven-artifact a maven-core contain the
> same classes. This causes the java9 compiler to fail. It also seems that
> those libraries haven't been upgraded to use module-info.java or at least
> automatic module name in META-INF.
> Expected solution:
> restructure the libraries to conform to the java module system.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
