[
https://issues.apache.org/jira/browse/MJAVADOC-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097387#comment-15097387
]
Christopher Tubbs commented on MJAVADOC-387:
--------------------------------------------
1. you are correct. It's only a workaround when used in a profile activated by
jdk8. I'm hoping that workaround is temporary and that m-j-p can address it
properly with this issue soon.
2. Yes, that's what I think it should do, only because it's not known in
advance which lint options will be available on a given javadoc version/tool.
But, it is reasonable to assume that they will support the {{-Xdoclint:group}}
syntax.
3. I'm not sure we need to do any validation at all. We can let the underlying
javadoc do that. As long as we don't split on commas, whitespace, etc. and
treat the value as a single argument, I think we can, and should, pass it
straight through.
> 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)
