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

Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/07/01 02:34:11 UTC

[jira] [Commented] (HBASE-16129) check_compatibility.sh is broken when using Java API Compliance Checker v1.7

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

Hudson commented on HBASE-16129:
--------------------------------

FAILURE: Integrated in HBase-1.4 #261 (See [https://builds.apache.org/job/HBase-1.4/261/])
HBASE-16129 check_compatibility.sh is broken when using Java API (busbey: rev aa361a20ced90d016dc45d6dd533a075e5f12b19)
* dev-support/check_compatibility.sh


> check_compatibility.sh is broken when using Java API Compliance Checker v1.7
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-16129
>                 URL: https://issues.apache.org/jira/browse/HBASE-16129
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: Dima Spivak
>            Assignee: Dima Spivak
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16129_v1.patch, HBASE-16129_v2.patch, HBASE-16129_v3.patch
>
>
> As part of HBASE-16073, we hardcoded check_compatiblity.sh to check out the v1.7 tag of Java ACC. Unfortunately, just running it between two branches that I know have incompatibilities, I get 0 incompatibilities (and 0 classes read). Looks like this version doesn't properly traverse through JARs.



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