Github user kscarr73 commented on the issue:
One problem I see, is that if someone has already included guava in their
project, or like me, use curator-client in an OSGI environment that already has
guava installed, this could cause conflicts.
I see 2 options:
1. Use Shade to change the package name for the guava stuff, so it doesn't
2. Create a different client project that is client-core or something
similar, and then build the client shade with guava from this.
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket