Return-Path: X-Original-To: apmail-curator-dev-archive@minotaur.apache.org Delivered-To: apmail-curator-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 30C5317275 for ; Tue, 1 Sep 2015 02:31:46 +0000 (UTC) Received: (qmail 20864 invoked by uid 500); 1 Sep 2015 02:31:46 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 20815 invoked by uid 500); 1 Sep 2015 02:31:46 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 20800 invoked by uid 99); 1 Sep 2015 02:31:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Sep 2015 02:31:46 +0000 Date: Tue, 1 Sep 2015 02:31:46 +0000 (UTC) From: "Mike Drob (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CURATOR-256) Provide curator artifact in Maven Central with Guava shaded away 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/CURATOR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724619#comment-14724619 ] Mike Drob commented on CURATOR-256: ----------------------------------- I think I would prefer the approach in CURATOR-200, since we still have Guava in our public API, attempting to shade it away might cause more problems than it solves. > Provide curator artifact in Maven Central with Guava shaded away > ---------------------------------------------------------------- > > Key: CURATOR-256 > URL: https://issues.apache.org/jira/browse/CURATOR-256 > Project: Apache Curator > Issue Type: Improvement > Reporter: Robert Metzger > Assignee: Jordan Zimmerman > > Guava is used by a lot of projects, often leading to version conflicts (Guava releases are incompatible). > A common solution to resolve this issue is to use the "maven-shade-plugin" and pack the (Apache licensed) guava classes into the curator jars. > The Flink project is currently adding a {{flink-shaded-curator}} Maven module which is shading Curator's Guava away, so that it does not affect our users or code: https://github.com/apache/flink/pull/1076/files > It would be great if Curator would directly provide an artifact in Maven central without a (visible) Guava dependency. > If the project agrees to add this feature, I'm willing to provide a patch/pull request for this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)