[ 
https://issues.apache.org/jira/browse/MJAVADOC-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958107#comment-17958107
 ] 

Olivier Lamy commented on MJAVADOC-721:
---------------------------------------

This project has moved from Jira to GitHub Issues. This issue was migrated to 
[apache/maven-javadoc-plugin#1091|https://github.com/apache/maven-javadoc-plugin/issues/1091].
 

> Parse stderr output and suppress informational lines
> ----------------------------------------------------
>
>                 Key: MJAVADOC-721
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-721
>             Project: Maven Javadoc Plugin (Moved to GitHub Issues)
>          Issue Type: Improvement
>          Components: javadoc
>    Affects Versions: 3.4.0
>            Reporter: Markus Spann
>            Assignee: Michael Osipov
>            Priority: Minor
>             Fix For: 3.5.0
>
>
> From Java 17 the Javadoc tool prints informational output to stderr mixed 
> with actual errors and warnings (see 
> [JDK-8268774|https://bugs.openjdk.org/browse/JDK-8268774], 
> [JDK-8270831|https://bugs.openjdk.org/browse/JDK-8270831]).
> Currently the maven-javadoc-plugin logs the complete content of the tool's 
> stderr as warning or includes it completely in the message of a 
> MavenReportException (in case of an unsuccessful exit code of the tool). This 
> behavior is not optimal with Java 17 onwards.
> The output can be lengthy and the informational messages very distracting. 
> This is particularly true for larger projects.
> This improvement enables the developer/user to focus on the actual warnings 
> or errors.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to