You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/09/01 09:06:00 UTC

[jira] [Commented] (HBASE-18622) Mitigate compatibility concerns between branch-1 and branch-2

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

stack commented on HBASE-18622:
-------------------------------

Here is how I generated the report:

{code}
$ ./dev-support/checkcompatibility.py --annotation org.apache.hadoop.hbase.classification.InterfaceAudience.Public --annotation org.apache.hadoop.hbase.classification.InterfaceAudience.LimitedPrivate 6c98bff7b719efdb16f71606f3b7d8229445eb81 a0f980b573b5af134002f0cb9163384d694b4388
{code}

I'd edited ./dev-support/checkcompatibiilty.py to use JACC 2.3  instead of 2.1 because it had this fix... https://github.com/lvc/japi-compliance-checker/issues/40 (via [~busbey]

Otherwise the reports are massive including privately annotated classes.

> Mitigate compatibility concerns between branch-1 and branch-2
> -------------------------------------------------------------
>
>                 Key: HBASE-18622
>                 URL: https://issues.apache.org/jira/browse/HBASE-18622
>             Project: HBase
>          Issue Type: Bug
>          Components: API
>            Reporter: stack
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 2.0.0-alpha-3
>
>
> This project is to do what [~apurtell] did in the issue "HBASE-18431 Mitigate compatibility concerns between branch-1.3 and branch-1.4" only do it between branch-1 and branch-2.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)