[
https://issues.apache.org/jira/browse/HBASE-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185624#comment-14185624
]
stack commented on HBASE-11912:
-------------------------------
It looks good up here Andrew after your patch went in:
https://builds.apache.org/view/H-L/view/HBase/job/HBase-TRUNK/5706/
Where I go to see the new errors? Or they only share if a patch violates? Is
there a 'count' of allowed bads? Thanks A.
> Catch some bad practices at compile time with error-prone
> ---------------------------------------------------------
>
> Key: HBASE-11912
> URL: https://issues.apache.org/jira/browse/HBASE-11912
> Project: HBase
> Issue Type: Sub-task
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 2.0.0
>
> Attachments: HBASE-11912.patch, HBASE-11912.patch, HBASE-11912.patch,
> HBASE-11912.patch
>
>
> Google's error-prone (https://code.google.com/p/error-prone/) wraps javac
> with some additional static analysis that will generate additional warnings
> or errors at compile time if certain bug patterns
> (https://code.google.com/p/error-prone/wiki/BugPatterns) are detected. What's
> nice about this approach, as opposed to findbugs, is the compile time
> detection and erroring out prevent the detected problems from getting into
> the codebase up front.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
