[
https://issues.apache.org/jira/browse/CURATOR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723490#comment-14723490
]
Jordan Zimmerman commented on CURATOR-256:
------------------------------------------
Why not shade all the dependencies? We could have a curator-deps project or
something that builds a shaded deps jar.
> 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)
