You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Dima Spivak (JIRA)" <ji...@apache.org> on 2015/12/04 20:34:11 UTC

[jira] [Created] (HBASE-14930) check_compatibility.sh needs smarter exit codes

Dima Spivak created HBASE-14930:
-----------------------------------

             Summary: check_compatibility.sh needs smarter exit codes
                 Key: HBASE-14930
                 URL: https://issues.apache.org/jira/browse/HBASE-14930
             Project: HBase
          Issue Type: Bug
            Reporter: Dima Spivak
            Assignee: Dima Spivak


The check_compatibility.sh tool in dev_support uses the Java API Compliance Checker to do static analysis of source/binary incompatibilties between two HBase branches. One problem, though, is that the script has a few instances where it may return an exit code of 1 (e.g. if Maven steps fail), but this is the same exit code that the Java ACC tool itself uses to denote that the tool succeeded, but found incompatibilities.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)