On Wed, Sep 03, 2014 at 07:40:38PM +0300, Inbar Stolberg wrote: > Regarding guava. > Jclouds is using guava 1.7 and is keeping up to date with the guava > versions the problem is not every one does and guava versions are not > backward compatible. > I am using casandara which the latest official release supports guava 1.5 > So to make Cassandra and jclouds work in the same module I needed to > downgrade jclouds to 1.6 (meddling in the code) and upgrade Cassandra to a > nun official release version. > I believe this gap will increase over time. And basically it means jclouds > won't provide backward compatibility due to third party jars. > Can any of the devs respond to this issue?
Historically jclouds uptakes new versions of Guava when Google releases them since they provide some desired functionality. Recently we have emphasized *forward* compatibility with Guava versions, removing uses of deprecated methods before future Guava releases remove them. We should also avoid use of @Beta annotated interfaces although we currently lack a way to enforce this. *Backward* compatibility could be an interesting goal; for example I made small changes to 1.8.x to allow compatibility with Guava 16[1]. If someone in the community wants to build on this commit we can include it in then next 1.8.x release. However, I would like to continue to eagerly upgrade Guava versions on master. [1] https://github.com/andrewgaul/jclouds/commit/bfcccd1d56df2a2c8b9bfcdc4720cfff4235d7f0 -- Andrew Gaul http://gaul.org/
