apache
[CURATOR-555] Curator Client leaks the com.google.guava:guava regardless of it being shaded.
The curator-client leaks the com.google.guava:guava regardless of it being shaded within the artifact.
com.google.guava guava
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.
Originally reported by berngp, imported from: Curator Client leaks the com.google.guava:guava regardless of it being shaded.
- status: Open
- priority: Minor
- resolution: Unresolved
- imported: 2025-01-21
Based on https://cwiki.apache.org/confluence/display/CURATOR/TN13 it looks like this will always be the case. Users can pin to the specific version they need/want.
Correct per that Tech Note. At some point, we can bite the bullet and make the breaking change.
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.