[
https://issues.apache.org/jira/browse/HBASE-18240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056706#comment-16056706
]
stack commented on HBASE-18240:
-------------------------------
I pushed first commit to the new repo. See
https://git-wip-us.apache.org/repos/asf?p=hbase-thirdparty.git It builds a
hbase-thirdparty-shaded jar. I pushed up a SNAPSHOT here:
https://repository.apache.org/content/groups/snapshots/org/apache/hbase/thirdparty/hbase-thirdparty-shaded/
Would appreciate review of what I've posted. Currently it shades guava 22.0 and
that is it. See https://git-wip-us.apache.org/repos/asf?p=hbase-thirdparty.git
Let me now work on a patch that makes hbase use the shaded guava.
> Add hbase-auxillary, a project with hbase utility including an
> hbase-shaded-thirdparty module with guava, netty, etc.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-18240
> URL: https://issues.apache.org/jira/browse/HBASE-18240
> Project: HBase
> Issue Type: Sub-task
> Components: dependencies
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0
>
> Attachments: HBASE-18240.master.001.patch, hbase-auxillary.tgz
>
>
> This issue is about adding a new related project to host hbase auxillary
> utility. In this new project, the first thing we'd add is a module to host
> shaded versions of third party libraries.
> This task comes of discussion held here
> http://apache-hbase.679495.n3.nabble.com/DISCUSS-More-Shading-td4083025.html
> where one conclusion of the DISCUSSION was "... pushing this part forward
> with some code is the next logical step. Seems to be consensus about taking
> our known internal dependencies and performing this shade magic."
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
