[
https://issues.apache.org/jira/browse/MJAVADOC-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096917#comment-15096917
]
Michael Osipov commented on MJAVADOC-387:
-----------------------------------------
Christopher, thank you for this analysis. Your approach is reasonable. I'd even
consider to apply it the way you proposed it. Though, I would like to clarify
some issues first:
1. Applying {{<additionalparam>-Xdoclint:none,...</additionalparam>}} is not a
solution (workaround) just because you need to do this within a profile?
2. This would be a passthrough without any validation of input. {{javadoc}}
will fail if you pass {{auto}} or else.
3. We need to be sure that all comma-passed values can be safely passed to a
single option of {{-Xdoclint:..}}.
> 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)
