You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2016/01/18 20:36:39 UTC
[jira] [Updated] (HBASE-14930) check_compatibility.sh needs smarter
exit codes
[ https://issues.apache.org/jira/browse/HBASE-14930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Enis Soztutar updated HBASE-14930:
----------------------------------
Fix Version/s: (was: 1.0.4)
1.0.3
> 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
> Fix For: 2.0.0, 1.2.0, 1.3.0, 1.0.3, 1.1.3, 0.98.17
>
> Attachments: HBASE-14930_master_v1.patch
>
>
> 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)