[
https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759668#comment-13759668
]
Nick Dimiduk commented on HBASE-9153:
-------------------------------------
a couple questions:
- is there a way to specify running the tool vs two refs from the same
repository? I don't understand how the 2nd and 4th parameter are used -- they
look like report labels when run vs local directory but branch names when repos
are used.
- how do I specify a local repo? Ie, retrieve branch 0.96 from
~/repos/hbase/.git ?
Running like so:
$ ./dev-support/jdiffHBasePublicAPI.sh https://github.com/apache/hbase.git 0.94
https://github.com/apache/hbase.git 0.96
I'm seeing lots of errors prefixed with [Javadoc for 0.94], lots of stuff I
don't recall seeing when I run mvm javadoc:javadoc. Is that expected?
> Create a deprecation policy enforcement check
> ---------------------------------------------
>
> Key: HBASE-9153
> URL: https://issues.apache.org/jira/browse/HBASE-9153
> Project: HBase
> Issue Type: Task
> Reporter: Jonathan Hsieh
> Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch,
> HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch
>
>
> We've had a few issues now where we've removed API's without deprecating or
> deprecating in the late release. (HBASE-9142, HBASE-9093) We should just
> have a tool that enforces our api deprecation policy as a release time check
> or as a precommit check.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
