[
https://issues.apache.org/jira/browse/MJAVADOC-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109788#comment-15109788
]
Sergei Ivanov commented on MJAVADOC-387:
----------------------------------------
If the above behaviour is going to be dependent on JDK version, m-j-p must
continue to work with java toolchain correctly. That is, if the java toolchain
is configured, then the java/javadoc version needs to be derived from the
toolchain, not from the JRE that is running Maven build. The toolchain (if
present) is currently being used to look up javadoc tool, therefore its
handling must be consistent.
As long as toolchains are supported, I'd be happy with [~ctubbsii] proposal.
> Handle JDK8 -Xdoclint
> ---------------------
>
> Key: MJAVADOC-387
> URL: https://issues.apache.org/jira/browse/MJAVADOC-387
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
> Reporter: scolebourne2
>
> The Oracle team have added the doclint tool to JDK 8. The tool validates
> Javadoc as part of a standard Javadoc run. Unfortunately, with the default
> settings, it rejects many HTML elements that are perfectly acceptable to
> browsers, and all invalid Javadoc references (@links). This is likely to
> prove very unpopular with developers.
> Action needed:
> 1) Provide a maven-javadoc-plugin configuration item and property that can
> control the doclint tool (currently this requires using additionalparam
> AFAICT).
> 2) Apply the {{-Xdoclint:none}} option by default, so that doclint is opt-in,
> not opt-out (ie. fix Oracle's messed up default). This will also make it much
> easier for developers to handle migration to JDK 8.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
