[
https://issues.apache.org/jira/browse/MJAVADOC-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958067#comment-17958067
]
Olivier Lamy commented on MJAVADOC-683:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#1065|https://github.com/apache/maven-javadoc-plugin/issues/1065].
> Reimplement failOnWarning
> -------------------------
>
> Key: MJAVADOC-683
> URL: https://issues.apache.org/jira/browse/MJAVADOC-683
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.3.1
>
>
> As of JDK 17 the STDERR is not just used for error output anymore.
> {quote}
> This is a deliberate change in policy, to match the equivalent `javac` policy.
> All diagnostic and logging output is now written to stderr when javadoc is
> invoked from the command line, leaving stdout to be used for output
> specifically requested by command-line options, like `--help` etc.
> {quote}
> The advice is: check the tail of the output written to stderr for lines
> reporting the number of errors and number of warnings.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
