[
https://issues.apache.org/jira/browse/HBASE-13126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340520#comment-14340520
]
Andrew Purtell commented on HBASE-13126:
----------------------------------------
bq. the hbase-testing-util module currently is just an aggregator. we could
restructure to move these things out of the src/test in hbase-server to there
+1
Curious what would be the practical impact of moving a class from
hbase-server-test to hbase-server. Both have to be on the classpath already in
order for tests to work, or as you mention, hbase-testing-util does the
aggregation. Strictly speaking moving a class from one jar to another is a
binary change incompatible on some level though.
> Clean up API for unintended methods within non-private classes.
> ---------------------------------------------------------------
>
> Key: HBASE-13126
> URL: https://issues.apache.org/jira/browse/HBASE-13126
> Project: HBase
> Issue Type: Task
> Components: API
> Affects Versions: 2.0.0
> Reporter: Sean Busbey
> Priority: Blocker
> Fix For: 2.0.0
>
>
> Over in the review for HBASE-12972, [~enis] mentioned that one of the HBTU
> methods wasn't intended for public consumption.
> Can we build a list of such methods across the API, appropriately annotate
> them for 2.0, and deprecate them in earlier versions with a warning that
> they're going to be restricted?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
