This is something we want to bring to the dev mailing list. The only problem with this is dropping compatibility with Guava < 19, which will probably have a big impact in users. However, if we don't do such a change in 2.0... then when?
Like @demobox, I'm a bit hesitant until we know a bit more about the Guava versions people are using now, although not that worried by the version gap between 1.9.x and 2.0. We already have the [guava/guice compatibility build](https://jclouds.ci.cloudbees.com/job/jclouds-guava-guice-compat/) and I'd say it should work for 1.9.x too. Despite Guava 16 being the default version we use, Guava 19 should be already supported, so users should be able to upgrade Guava without upgrading jclouds, when planning a future upgrade to 2.0. We should run a Guava 19 build against 1.9.x and, if it succeeds, I'd be happy to have this merged as soon as we document a smooth upgrade plan for users willing to upgrade to 2.0. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/982#issuecomment-232561019
