Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 27 Oct 2014 04:07:33 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12739916.1410197068000.342318.1414382853894@Atlassian.JIRA>
In-Reply-To: <JIRA.12739916.1410197068000@Atlassian.JIRA>
References: <JIRA.12739916.1410197068000@Atlassian.JIRA>
 <JIRA.12739916.1410197068878@arcas>
Subject: [jira] [Commented] (HBASE-11912) Catch some bad practices at
 compile time with error-prone
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-11912:
-------------------------------

You commit your fixup [~apurtell]?  Looks like we need this (smile).  See over in HBASE-12187.

> 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
>         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)