[
https://issues.apache.org/jira/browse/MJAVADOC-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16098984#comment-16098984
]
Matt Nelson commented on MJAVADOC-387:
--------------------------------------
Just came across this since the milestone was released this week. Should the
user property be name spaced to the plugin context? {{maven.javadoc.doclint}}
vs {{doclint}}. Name spaced user properties make it clearer to understand the
intent when defined via command line or the properties block away from the
actual plugin block.
> Handle JDK8 -Xdoclint
> ---------------------
>
> Key: MJAVADOC-387
> URL: https://issues.apache.org/jira/browse/MJAVADOC-387
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
> Components: javadoc
> Affects Versions: 2.10.4
> Reporter: scolebourne2
> Assignee: Michael Osipov
> Fix For: 3.0.0, 3.0.0-M1
>
>
> 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.4.14#64029)
