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

Enis Soztutar updated HBASE-12808:
----------------------------------
    Attachment: 0.98.9_branch-1.0_compat_report.html

Attaching a report from 0.98.9 -> branch-1.0 comparison. This is quite useful. 

>From the report, the changes does not seem concerning to me. There are some 
>source compat changes for sure, but mostly manageable from applications. But 
>feel free to double check, I may have missed something. 

> 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: 0.98.9_branch-1.0_compat_report.html, 
> HBASE-12808_v1.patch, HBASE-12808_v2.patch, HBASE-12808_v3.patch, 
> HBASE-12808_v4.patch, HBASE-12808_v5.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