[
https://issues.apache.org/jira/browse/MJAVADOC-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698338#comment-16698338
]
Hudson commented on MJAVADOC-506:
---------------------------------
Build succeeded in Jenkins: Maven TLP » maven-javadoc-plugin » master #76
See
https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/master/76/
> Javadoc plugin broken on Java 8 when module-info.java present
> -------------------------------------------------------------
>
> Key: MJAVADOC-506
> URL: https://issues.apache.org/jira/browse/MJAVADOC-506
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 3.0.0
> Reporter: Stephen Colebourne
> Assignee: Robert Scholte
> Priority: Major
>
> The fix to MJAVADOC-498 causes the command line flag `--class-path` to be
> used on Java 8, a flag that is not recognised. This happens when the project
> contains `module-info.java`, but the module-info file is excluded by the
> configuration of the plugin.
> The problem is here:
> http://svn.apache.org/viewvc/maven/plugins/trunk/maven-javadoc-plugin/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java?r1=1802722&r2=1813672&pathrev=1813672
> where the code checks whether `src/main/java/module-info.java` exists without
> considering whether the file has been excluded by configuration. (I am simply
> trying to setup a build that uses Java 9 tooling on Java 9 and Java 8 tooling
> when running on Java 8)
> There is no workaround to this in v3.0.0 that I can see, so I have to
> rollback to v3.0.0-M1. The solution is to check the includes/excludes when
> trying to obtain the module-info file. Or to check what version of the
> Javadoc tool is being used (as per MJAVADOC-499).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
