curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Blum (JIRA)" <>
Subject [jira] [Commented] (CURATOR-256) Provide curator artifact in Maven Central with Guava shaded away
Date Tue, 01 Sep 2015 14:47:45 GMT


Scott Blum commented on CURATOR-256:

Later releases of Guava are largely backwards compatible with older ones.  The easiest thing
to do with Maven is generally that in your final project, you simply override the transitive
dep from curator -> guava with a version you choose.

Supposing an end-user did this, are there specific Guava APIs we're using that are problematic?

> Provide curator artifact in Maven Central with Guava shaded away
> ----------------------------------------------------------------
>                 Key: CURATOR-256
>                 URL:
>             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:
> 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

View raw message