Can any of the devs respond to this issue?
jclouds uses Guava pretty heavily, including some of the newer features that were added in more recent releases (Andrew G can probably provide much more technical detail here). In some instances, such as fixing JCLOUDS-427 [1], we actually *depend* on newer Guava versions.
In short, from what I know, sticking to older Guava versions is not really an option for new jclouds major versions going forward.
Which leaves two questions for me: support for older Guava versions by supporting older jclouds major releases, and looking for the conflicting projects/products to work with newer Guava versions.
For the former: we have historically tried to support the current major version and the former major version (which means 1.8.x and 1.7.x for now). Support for the prior major version tends to be limited to critical fixes rather than ongoing backporting of everything that's making it onto master.
So you should still be able to use an older version of Guava by sticking to an older jclouds major version, but you are unlikely to be able to make use of significant new jclouds features. From what I can see, we simply don't have the bandwidth in the active developer community to handle all the backports and minor releases for older versions.
Which leaves the final point: is there some way to "encourage" the projects you are using that are stuck on older versions to upgrade? It does seem to me that they're slightly more responsible for causing this problem than jclouds is. I know that is easy to say and doesn't help resolve the issue, but if we can help by adding our voice to "Upgrade Guava version please" discussions I'm happy to pitch in.
In the case of Cassandra, by the way, I'm glad to see this discussion is already happening:
https://issues.apache.org/jira/browse/CASSANDRA-6639 Regards ap [1] https://issues.apache.org/jira/browse/JCLOUDS-427
