hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13517) Publish a client artifact with shaded dependencies
Date Tue, 21 Apr 2015 15:47:59 GMT

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

Sean Busbey commented on HBASE-13517:
-------------------------------------

{quote}
Can we avoid including things in the shaded jar that aren't in org.apache.hadoop.hbase or
subpackages? That's probably the #1 source of pain with shaded artifacts.
{quote}

this should have been "aren't relocated in". I don't want e.g. someone who needs to use HBase
and HDFS to suddenly have another jar with the hadoop packages visible just because they're
trying to use our shaded artifact.

> 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.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