You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Allen Wittenauer (Jira)" <ji...@apache.org> on 2020/09/07 20:19:00 UTC

[jira] [Updated] (YETUS-554) javadoc plug-in should be more explicit

     [ https://issues.apache.org/jira/browse/YETUS-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer updated YETUS-554:
-----------------------------------
    Fix Version/s:     (was: 0.13.0)

> javadoc plug-in should be more explicit
> ---------------------------------------
>
>                 Key: YETUS-554
>                 URL: https://issues.apache.org/jira/browse/YETUS-554
>             Project: Yetus
>          Issue Type: Improvement
>          Components: Precommit
>    Affects Versions: 0.6.0
>            Reporter: Allen Wittenauer
>            Priority: Critical
>
> Normally, yetus treats build failures as a "show the whole log" situation.  In the case of Javadoc and projects with thousands and thousands of warnings (e.g., Hadoop), the errors that caused the javadoc failure get completely missed.  Committers treat these errors as just a temporary failure (!) since they can't find the fault.  
> In the case of javadoc, we should specifically do *two* failure checks:
> 1) Normal build failure output
> 2) Check for an '[ERROR] ... error: ... ' string and print that output into a separate log.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)