Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 14 Dec 2012 21:54:12 +0000 (UTC)
From: "nkeywal (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12623844.1355437726307.9130.1355522052877@arcas>
In-Reply-To: <JIRA.12623844.1355437726307@arcas>
References: <JIRA.12623844.1355437726307@arcas>
Subject: [jira] [Commented] (HBASE-7349) Jenkins build should compare trunk
 vs patch for Javadoc warnings
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532702#comment-13532702 ] 

nkeywal commented on HBASE-7349:
--------------------------------

Ok, so I will do the ones I mentioned... But tomorrow now :-). There will be less risk of conflict.
                
> Jenkins build should compare trunk vs patch for Javadoc warnings
> ----------------------------------------------------------------
>
>                 Key: HBASE-7349
>                 URL: https://issues.apache.org/jira/browse/HBASE-7349
>             Project: HBase
>          Issue Type: Improvement
>          Components: build
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Minor
>         Attachments: 7349-build-improve-javadoc-warnings.0.diff
>
>
> The javadoc check should look for an increase in the number of warnings. It can do so by running javadoc against trunk before running it for the patch. This will increase build times.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira