[
https://issues.apache.org/jira/browse/HBASE-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532512#comment-13532512
]
stack commented on HBASE-7349:
------------------------------
I like the moving stuff to zero rather than double running javadoc-ery. Lets
just make patches for a bunch over in new issues, review each others work
quickly and get them in. We should do same for findbugs? I volunteer for
hbase-common, hbase-protocol, and hbase-client... starting now.
> 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
