You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Martin Desruisseaux (JIRA)" <ji...@codehaus.org> on 2014/04/19 06:27:10 UTC

[jira] (MJAVADOC-387) Handle JDK8 -Xdoclint

    [ https://jira.codehaus.org/browse/MJAVADOC-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345104#comment-345104 ] 

Martin Desruisseaux commented on MJAVADOC-387:
----------------------------------------------

A support for {{-Xdoclint}} would be appreciated. However I disagree that Maven should take {{-Xdoclint:none}} as the default. I realize that the JDK 8 behavior (all checks enabled by default) will break lot of Javadoc generation. But I think that it is preferable to force developers to explicitly disable the checks if they need too, otherwise many developers will probably not even realize that their Javadoc has problems. Especially since when using {{-Xdoclint:none}}, the errors are not replaced by warnings - they just disappear.

> Handle JDK8 -Xdoclint
> ---------------------
>
>                 Key: MJAVADOC-387
>                 URL: https://jira.codehaus.org/browse/MJAVADOC-387
>             Project: Maven Javadoc Plugin
>          Issue Type: Improvement
>            Reporter: Stephen Colebourne
>
> 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.1.6#6162)