[
https://issues.apache.org/jira/browse/MJAVADOC-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358150#comment-16358150
]
Andy Seaborne edited comment on MJAVADOC-511 at 2/9/18 9:27 AM:
----------------------------------------------------------------
There are many blog pages describing the use of
{{<additionalparam>-Xdoclint:none</additionalparam>}}. It would be helpful to
at least warn when this is used and ignored.
I encountered this effect while upgrading a build to work with Java9 using the
information in
https://cwiki.apache.org/confluence/display/MAVEN/Java+9+-+Jigsaw
was (Author: andy.seaborne):
There are many blog pages describing the use of
{{<additionalparam>-Xdoclint:none</additionalparam>}}. It would be helpful to
at least warn when this is used and ignored.
> Doclint regression in 3.0.0
> ---------------------------
>
> Key: MJAVADOC-511
> URL: https://issues.apache.org/jira/browse/MJAVADOC-511
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 3.0.0
> Reporter: Aurélien
> Assignee: Robert Scholte
> Priority: Major
>
> Before 3.0.0 it was possible to disable doclint validation by using the
> parameter {{}}
> {code:java}
> <additionalparam>-Xdoclint:none</additionalparam>{code}
>
> Since 3.0.0 this parameter is ignored and the javadoc plugin raises many
> errors again.
>
> I understand there is a new parameter, "doclint", to control the doclint
> validation. However, if the "old way" is not the intended way, would it be
> possible to deprecate the old option (and show a warning) before actually
> removing this parameter?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
