[
https://issues.apache.org/jira/browse/HBASE-18240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055121#comment-16055121
]
stack commented on HBASE-18240:
-------------------------------
[~busbey] Help would be appreciated especially if you've been this route before.
I'm thinking new repo called hbase-auxillary. That ok? Was thinking we could
host various little related projects here with the first one being 3rdparty
shaded.
I'd have a root project and then a first module called hbase-3rdparty-shaded.
This module would produce shaded and relocated 3rd party libs.
groupid = org.apache.hbase.auxillary
Relocation would be from com.google.* to
org.apache.hbase.3rdparty.shaded.com.google.* etc.
Let me attach what I have currently.
But yeah, request for repo appreciated.
> 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
>
>
> 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)
