hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13517) Publish a client artifact with shaded dependencies
Date Wed, 22 Apr 2015 20:43:59 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507855#comment-14507855
] 

Elliott Clark commented on HBASE-13517:
---------------------------------------

Thoughts on this?

I've tested that the client jar works and I can use it to scan data from a cluster.
There are no deps other than hadoop that aren't relocated.
Guava and others can be on the classpath with different versions and everything works well.

> Publish a client artifact with shaded dependencies
> --------------------------------------------------
>
>                 Key: HBASE-13517
>                 URL: https://issues.apache.org/jira/browse/HBASE-13517
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0, 1.1.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>             Fix For: 2.0.0, 1.1.0
>
>         Attachments: HBASE-13517-v1.patch, HBASE-13517-v2.patch, HBASE-13517-v3.patch,
HBASE-13517.patch
>
>
> Guava's moved on. Hadoop has not.
> Jackson moves whenever it feels like it.
> Protobuf moves with breaking point changes.
> While shading all of the time would break people that require the transitive dependencies
for MR or other things. Lets provide an artifact with our dependencies shaded. Then users
can have the choice to use the shaded version or the non-shaded version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message