[
https://issues.apache.org/jira/browse/HBASE-18240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16060461#comment-16060461
]
stack commented on HBASE-18240:
-------------------------------
Pushed new patch on hbase-thirdparty. hbase-thirdparty has guava, gson, netty,
and protobuf-util but not protobuf itself. Compiling the fat patched jar that
included protobuf and guava and netty, etc., failed; dependencies of guava
(errorprone) and netty src are not available so the compile fails. Will leave
the production of the protobuf as is in hbase-protocol-shaded for now. Will
come back and experiment with a multi-module build under hbase-thirdparty
later; one module will do protobuf patching and then next module will do the
shade of it all -- no compile.
> Add hbase-thirdparty, 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)
