[
https://issues.apache.org/jira/browse/YETUS-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215217#comment-17215217
]
Allen Wittenauer commented on YETUS-554:
----------------------------------------
Linking YETUS-1028 because I think this will fix the difference engine to be
significantly smarter for javac and javadoc.
> 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)
