[
https://issues.apache.org/jira/browse/MJAVADOC-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333701#comment-16333701
]
Aurélien commented on MJAVADOC-511:
-----------------------------------
I do not understand why changing it in another version would be worse. You
could have deprecated this old parameter and create the new one.
But anyway it looks like you do not want to go back on this decision.
However, maybe it would be possible to communicate about this change?
An idea would be to put a paragraph about this breaking change in
[https://maven.apache.org/plugins/maven-javadoc-plugin/index.html]
In this paragraph including an example describing the change to do in the
pom.xml to be compatible with the version 3.0.0 of the plugin would be nice.
> 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)
