hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8344) Improve test-patch to make it easier to find javadoc warnings
Date Thu, 03 May 2012 18:54:49 GMT

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

Todd Lipcon updated HADOOP-8344:

    Attachment: sketch.txt

I was thinking something like this (this isn't really tested yet, was half done but figured
I'd post so people could see my thinking)
> 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
>         Attachments: sketch.txt
> 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
> - 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


View raw message