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

Andrew Purtell commented on HBASE-12808:
----------------------------------------

How would one use this to check the compatibility of an unreleased build? 

I applied the patch on this issue to branch 0.98, and did this:
{noformat}
$ mkdir dev-support/compatibility/1  
$ mkdir dev-support/compatibility/2
$ cp -a .git dev-support/compatibility/1  
$ cp -a .git dev-support/compatibility/2
$ ( cd dev-support/compatibility/1 && git co -f 0.98.9 ) # <-- this is a tag
$ ( cd dev-support/compatibility/2 && git co -f HBASE-12729-0.98 ) # <-- this 
is a local branch
$ bash dev-support/check_compatibility.sh -n 0.98.9 HBASE-12729-0.98
The JARs to be analyzed from 0.98.9 are:
The JARs to be analyzed from HBASE-12729-0.98 are:
Downloading Java API Compliance Checker...
Cloning into 'dev-support/compatibility/javaACC'...
remote: Counting objects: 203, done.
remote: Total 203 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (203/203), 149.26 KiB | 0 bytes/s, done.
Resolving deltas: 100% (128/128), done.
Checking connectivity... done.
Running the Java API Compliance Checker...
ERROR: can't access '-d2'
{noformat}
Didn't work.

> Use Java API Compliance Checker for binary/source compatibility
> ---------------------------------------------------------------
>
>                 Key: HBASE-12808
>                 URL: https://issues.apache.org/jira/browse/HBASE-12808
>             Project: HBase
>          Issue Type: Improvement
>          Components: test
>            Reporter: Dima Spivak
>            Assignee: Dima Spivak
>         Attachments: HBASE-12808_v1.patch, HBASE-12808_v2.patch, 
> HBASE-12808_v3.patch
>
>
> Following [~busbey]'s suggestion in HBASE-12556, I've spent some time playing 
> with the [Java API Compliance 
> Checker|http://ispras.linuxbase.org/index.php/Java_API_Compliance_Checker] 
> and think it would be a great addition to /dev-support. I propose that we use 
> it to replace the JDiff wrappers we currently have there (since it does what 
> JDiff does and more), and look into putting up automation at 
> builds.apache.org to run the tool regularly (e.g. latest release of a 
> particular branch vs. latest commit of that same branch).



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

Reply via email to