[
https://issues.apache.org/jira/browse/HBASE-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532172#comment-13532172
]
nkeywal commented on HBASE-7349:
--------------------------------
For javadocs warnings, would it make sense to fix all of them in trunk?
Then the count would be zero, and it any error would be a real one.
I know it's a boring job, but may be it's the easiest path. And it fixes the
root issue.
I don't mind doing it or participating if there are other volunteers.
For findbugs, the story is a little bit different as we can introduce bugs when
fixing them, but may be we should do that. As well, I expect it's possible to
annotate the code to deactivate locally a warning.
> 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
