hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14930) check_compatibility.sh needs smarter exit codes
Date Sat, 05 Dec 2015 00:12:10 GMT

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

Andrew Purtell commented on HBASE-14930:
----------------------------------------

lgtm, if no concerns will commit soon everywhere

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

Mime
View raw message