hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dima Spivak (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-14930) check_compatibility.sh needs smarter exit codes
Date Fri, 04 Dec 2015 19:40:11 GMT

     [ https://issues.apache.org/jira/browse/HBASE-14930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Dima Spivak updated HBASE-14930:
    Attachment: HBASE-14930_master_v1.patch

Patch that changes the exit codes we use during the setup before running the tool from "1"
to "2." This lets us continue to use the script's exit code overall as the exit code of the
Java API Compliance Checker tool.

> 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

View raw message