[
https://issues.apache.org/jira/browse/HADOOP-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267586#comment-13267586
]
Tom White commented on HADOOP-8344:
-----------------------------------
As a start, to make it easier to find the warnings, we could simply add a link
to the output of test-patch for the Jenkins job (e.g.
https://builds.apache.org/job/PreCommit-HADOOP-Build/928/) which lists all the
warnings files.
> Improve test-patch to make it easier to find javadoc warnings
> -------------------------------------------------------------
>
> Key: HADOOP-8344
> URL: https://issues.apache.org/jira/browse/HADOOP-8344
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build, test
> Reporter: Todd Lipcon
> Priority: Minor
>
> Often I have to spend a lot of time digging through logs to find javadoc
> warnings as the result of a test-patch. Similar to the improvement made in
> HADOOP-8339, we should do the following:
> - test-patch should only run javadoc on modules that have changed
> - the exclusions "OK_JAVADOC" should be per-project rather than cross-project
> - rather than just have a number, we should check in the actual list of
> warnings to ignore and then fuzzy-match the patch warnings against the
> exclude list.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
