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] [Updated] (HBASE-13517) Publish a client artifact with shaded dependencies
Date Tue, 28 Apr 2015 17:05:07 GMT

     [ https://issues.apache.org/jira/browse/HBASE-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Elliott Clark updated HBASE-13517:
----------------------------------
    Release Note: 
HBase now provides added convince artifacts that shade most dependencies. These jars hbase-shaded-client
and hbase-shaded-server are meant to be used when dependency conflicts can not be solved any
other way. The normal jars hbase-client and hbase-server should still be preferred when possible.

Do not use hbase-shaded-server or hbase-shaded-client inside of a co-processor as bad things
will happen.

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