[
https://issues.apache.org/jira/browse/MJAVADOC-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17382906#comment-17382906
]
Robert Scholte commented on MJAVADOC-683:
-----------------------------------------
Their argument is that we should have never assumed that output to STDERR
implies warnings.
I guess when they introduced STDOUT and STDERR they never thought about where
to write diagnostics to, this kind is now missing.
Overall this choice should indeed lead to more consistency, even though not
perfect.
> Reimplement failOnWarning
> -------------------------
>
> Key: MJAVADOC-683
> URL: https://issues.apache.org/jira/browse/MJAVADOC-683
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Major
>
> 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.3.4#803005)