[
https://issues.apache.org/jira/browse/CURATOR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725558#comment-14725558
]
Mike Drob commented on CURATOR-256:
-----------------------------------
bq. Later releases of Guava are largely backwards compatible with older ones.
I'm not sure that this is the case yet. Guava is one of the libraries I trust
_least_ w.r.t. compatibility.
bq. The Guava classes will appear as if they were from curator
Ok. I'm just thinking about the impact that this will have on our public API
where folks are currently using Guava classes. They'll have to replace them
with our relocated versions, right?
> 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)
