[
https://issues.apache.org/jira/browse/MJAVADOC-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254203#comment-16254203
]
Robert Scholte commented on MJAVADOC-499:
-----------------------------------------
If I add a {{module-info.java}} to my project, I expect it to be compiled and
added to my classes. If somebody uses an older version of Java, I would like to
see the build break to make that developer aware that must use Java 9 to
compile this project. The module descriptor contains to much important info to
be simply ignored.
Even though javadoc is about reporting, I prefer to let it behave as strict as
the maven-compiler-plugin.
I can only imagine that if the module descriptor was NOT compiled, then this
file can be ignored as well for javadoc. In fact: all compiled classes should
match all javadoc sourcefiles.
> Ignore module-info.java on earlier Java versions
> ------------------------------------------------
>
> Key: MJAVADOC-499
> URL: https://issues.apache.org/jira/browse/MJAVADOC-499
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
> Affects Versions: 3.0.0-M1
> Reporter: Stephen Colebourne
> Assignee: Robert Scholte
> Fix For: 3.0.0
>
>
> Versions of the javadoc tool prior to Java 9 cannot process
> `module-info.java`. The plugin should automatically detect and exclude
> `module-info.java` if the javadoc tool is Java 8 or earlier. The alternative
> (Java version specific profiles) does work, but is very verbose for something
> that can never work (thus the plugin should deal with it)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
