[
https://issues.apache.org/jira/browse/MJAVADOC-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249529#comment-16249529
]
Stephen Colebourne commented on MJAVADOC-499:
---------------------------------------------
Java 9 is not an LTS version, so many projects are going to need to have their
projects still compile and build on Java 8. The linked pom.xml ensures that
releases are done on Java 9, but there is no requirement for anyone other than
the person doing the release to use Java 9.
ie. a pom.xml is never just for a single maintainer in an OSS project - anyone
might come along and want to build it for their own needs. And since Java 9
isn't a long-lived LTS release, it won't be unusual for people to have Java 8,
but not Java 9. I'd expect many OSS projects to want to compile on both the
last LTS and the most current release, making use of additional features like
module-info where possible.
This request is very similar to cases when flags get added. For example,
doclint flag only exists in Javadoc from v8, but the plugin knows this and
doesn't try to use the flag when running older versions of Javadoc. Here, the
Javadoc plugin knows that older versions of Javadoc can't cope with
module-info, so it would exclude it.
> 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)
