Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E27E910A28 for ; Wed, 24 Dec 2014 19:38:13 +0000 (UTC) Received: (qmail 57574 invoked by uid 500); 24 Dec 2014 19:38:13 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 57487 invoked by uid 500); 24 Dec 2014 19:38:13 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 57475 invoked by uid 99); 24 Dec 2014 19:38:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Dec 2014 19:38:13 +0000 Date: Wed, 24 Dec 2014 19:38:13 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HBASE-3518) shade some of our dependencies to make some client's life easier MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-3518. ----------------------------------- Resolution: Incomplete Assignee: (was: ryan rawson) Incomplete dead issue > shade some of our dependencies to make some client's life easier > ---------------------------------------------------------------- > > Key: HBASE-3518 > URL: https://issues.apache.org/jira/browse/HBASE-3518 > Project: HBase > Issue Type: Improvement > Components: build > Affects Versions: 0.90.0 > Reporter: ryan rawson > Attachments: HBASE-shade-jar.txt > > > Clients who wish to use thrift, protobuf, avro and who include our classpath on their classpath run into incompatibilities, for example my client might depend on protobuf 2.1 but we ship 2.3.0, if there are any incompatible APIs then I won't be able to run my stuff by including HBase's classpath, nor will I be able to use bin/hbase to run my stuff. > We can help by using maven shade to include then rename some dependencies into the hbase*.jar itself, thus ensuring that they won't leak out. We could also build an all inclusive JAR that includes ALL our core dependencies, although we probably might want to skip including Hadoop since that is frequently switched out. Then a user would be able to include hbase*.jar and run. > This might not play well with the maven build and transitive export thing, we should probably think about it a bit more. > My initial list was: > - avro > - protobuf > - thrift -- This message was sent by Atlassian JIRA (v6.3.4#6332)