You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/10/14 13:09:00 UTC
[jira] [Comment Edited] (MJAVADOC-735) Analyze javadoc output and output individual log statements for warning and errors
[ https://issues.apache.org/jira/browse/MJAVADOC-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617723#comment-17617723 ]
Michael Osipov edited comment on MJAVADOC-735 at 10/14/22 1:08 PM:
-------------------------------------------------------------------
Javadoc is a troublesome fellow since they change the std streams from release to release :-(
was (Author: michael-o):
Javadoc is a troublesome fellow since they change the std streams from release to relase :-(
> Analyze javadoc output and output individual log statements for warning and errors
> ----------------------------------------------------------------------------------
>
> Key: MJAVADOC-735
> URL: https://issues.apache.org/jira/browse/MJAVADOC-735
> Project: Maven Javadoc Plugin
> Issue Type: Task
> Reporter: Guillaume Nodet
> Priority: Major
>
> When a javadoc fails, the few errors can be very difficult to find inside the maven log when there are a lot of warnings. In particular, all warnings are then displayed as errors and it is very unintuitive that a few errors cause the problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)