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 2017/10/10 19:07:02 UTC

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

Allen Wittenauer created YETUS-554:
--------------------------------------

             Summary: 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: Test Patch
    Affects Versions: 0.6.0
            Reporter: Allen Wittenauer
            Priority: Critical
             Fix For: 0.6.0


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
(v6.4.14#64029)