[
https://issues.apache.org/jira/browse/HBASE-16129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355720#comment-15355720
]
Andrew Purtell commented on HBASE-16129:
----------------------------------------
bq. it looks like there are several changes on master that didn't make it back
to branch-1. how about I make a jira that's essentially "copy the current state
of the compatibility checker"?
Please
bq. or a docs change for the release section to copy it like we do for the docs?
Well docs copy back to 0.98 doesn't work any more so I haven't done that for
several releases. We haven't made changes in 0.98 that invalidate the docs that
ship with it. HBASE-14792 documents that problem. I don't see a reason why copy
back of dev-support from master to 0.98 won't work today, but it might not
tomorrow
> 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)
