[
https://issues.apache.org/jira/browse/HBASE-20223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412143#comment-16412143
]
Josh Elser commented on HBASE-20223:
------------------------------------
{quote}Good eye. Definitely at least one thing to remove there. Building those
artifacts and poking at them now.
{quote}
Actually, I take it back. Because our hbase-shaded-client is using Hadoop
artifacts directly (and not the hadoop shaded artifacts), we have to shade
their commons-cli 1.2 and commons-collections 3, even though we use neither
(and have them banned) in our tree. That's fun :)
> Use hbase-thirdparty 2.1.0
> --------------------------
>
> Key: HBASE-20223
> URL: https://issues.apache.org/jira/browse/HBASE-20223
> Project: HBase
> Issue Type: Task
> Components: dependencies
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-20223.001.patch, HBASE-20223.002.branch-2.0.patch
>
>
> Update hbase to account for the changes to hbase-thirdparty:
> * new (internal) protobuf version
> * shaded commons-cli
> * shaded commons-collections4
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
