[ https://issues.apache.org/jira/browse/MJAVADOC-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17599303#comment-17599303 ]
Hudson commented on MJAVADOC-721: --------------------------------- Build succeeded in Jenkins: Maven » Maven TLP » maven-javadoc-plugin » master #36 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-javadoc-plugin/job/master/36/ > Parse stderr output and suppress informational lines > ---------------------------------------------------- > > Key: MJAVADOC-721 > URL: https://issues.apache.org/jira/browse/MJAVADOC-721 > Project: Maven Javadoc Plugin > Issue Type: Improvement > Components: javadoc > Affects Versions: 3.4.0 > Reporter: Markus Spann > Assignee: Michael Osipov > Priority: Minor > Fix For: 3.4.2 > > > 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)