[
https://issues.apache.org/jira/browse/HBASE-15666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127133#comment-16127133
]
Sean Busbey commented on HBASE-15666:
-------------------------------------
if you make a downstream client that uses the shaded client (e.g. [YCSB's
hbase12
implementation|https://github.com/brianfrankcooper/YCSB/tree/master/hbase12]),
you can't run any hbase minicluster based tests because the
hbase-testing-utility artifact pulls in all of the third party dependencies
that were removed by using the shaded client in the first place.
so either we need a new module, i.e.
{{hbase-shaded/hbase-shaded-testing-util}}, that shades the
{{hbase-testing-util}} module in the same way we shade the client, or we can
convert {{hbase-testing-util}} into a shaded jar (right now it is an empty jar
that pulls in the transitive dependencies needed to use our tesitng stuff). If
we do the latter, we need to make sure it works when testing non-shaded client
use (unless we also switch to using the shaded client by default)
now that I write this out, I'm not sure I've actually made things clearer. did
that help?
> shaded dependencies for hbase-testing-util
> ------------------------------------------
>
> Key: HBASE-15666
> URL: https://issues.apache.org/jira/browse/HBASE-15666
> Project: HBase
> Issue Type: New Feature
> Components: test
> Affects Versions: 1.1.0, 1.2.0
> Reporter: Sean Busbey
> Priority: Critical
> Fix For: 1.5.0, 2.0.0-alpha-2
>
>
> Folks that make use of our shaded client but then want to test things using
> the hbase-testing-util end up getting all of our dependencies again in the
> test scope.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
