[
https://issues.apache.org/jira/browse/HBASE-18240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-18240:
--------------------------
Release Note:
Adds a new project, hbase-thirdparty, at
https://git-wip-us.apache.org/repos/asf/hbase-thirdparty used by core hbase.
This project packages relocated third-party libraries used by Apache HBase such
as protobuf, guava, and netty among others. HBase core depends on it.
It has two submodules, one to patch and then relocate (shade) protobuf. The
other modules relocate a bundle of other (unpatched) libs used by hbase. This
latter set includes protobuf-util, netty-all, gson, and guava.
All shading is done using the same relocation offset of
org.apache.hadoop.hbase.shaded; we add this prefix to the relocated thirdparty
library class names.
See the pom.xml for the explicit version of each third-party lib included (of
note, we update out internal protobuf from 3.1.0 to 3.3.1).
Note that in hbase-shaded-protobuf, we unzip the protobuf jar to src/main/java
rather than to a dir under target because the jar plugin wants src here (its
hard to convince it otherwise).
> 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)
