[
https://issues.apache.org/jira/browse/HBASE-16129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-16129:
--------------------------------
Attachment: HBASE-16129_v3.patch
Attaching a patch that I think this fixes things once and for all. The problem
we were having had to do with our specification of annotations; whereas in the
past we could just provide a simple name, later versions of Java ACC require
specification of the canonical name. With that in place, things seem to behave
again.
> 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
> 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)
