[ https://issues.apache.org/jira/browse/HBASE-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534199#comment-13534199 ]
Nick Dimiduk commented on HBASE-7349: ------------------------------------- [~stack] This patch was committed also, so the build daemon will continue to run the javadoc target twice and compare results. It only adds about 3 minutes per build, so I think it's worth keeping, but you may disagree. > 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