[
https://issues.apache.org/jira/browse/CURATOR-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716277#comment-17716277
]
Kezhu Wang commented on CURATOR-555:
------------------------------------
Ideally, CURATOR-558 should unblock this in upgrading to 5.5.0. But CURATOR-670
leaks guava to public still. To solve this, we have to either break something
or postpone to next major release.
> Curator Client leaks the com.google.guava:guava regardless of it being shaded.
> ------------------------------------------------------------------------------
>
> Key: CURATOR-555
> URL: https://issues.apache.org/jira/browse/CURATOR-555
> Project: Apache Curator
> Issue Type: Bug
> Components: Client
> Affects Versions: 4.2.0
> Reporter: Bernardo Gomez Palacio
> Priority: Minor
>
> The curator-client leaks the {{com.google.guava:guava}} regardless of it
> being shaded within the artifact.
> {code:xml|title=https://search.maven.org/remotecontent?filepath=org/apache/curator/curator-client/4.2.0/curator-client-4.2.0.pom}
> <dependency>
> <groupId>com.google.guava</groupId>
> <artifactId>guava</artifactId>
> </dependency>
> {code}
> Note that since {{curator-client}} 4.2.0 was moved to Guava 27.0.1 as pat of
> CURATOR-502 this can cause problems for projects which depend on older
> versions of Guava but get upgraded by the transitive dependency to 27.0.1.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
