> This is something we want to bring to the dev mailing list...we should run a > Guava 19 build against 1.9.x
Sounds like a good plan to me. > Despite Guava 16 being the default version we use, Guava 19 should be already > supported It's not so much that we already support 19 that I'm concerned about, more that we currently allow users of our stable version to use any Guava version from 16 upwards. If we move to 19, that will force all stable users to jump up to 3 major versions (two years of development) of a commonly-used library, and we don't know how many other libraries they might be using which are **not** compatible with Guava 19? There's a decent amount of changes from 16 to 19: * http://google.github.io/guava/releases/17.0/api/diffs/ * http://google.github.io/guava/releases/18.0/api/diffs/ * http://google.github.io/guava/releases/19.0/api/diffs/ Having said that, I agree that 2.0 would be the most obvious time to consider this. Still, I'd want to avoid a situation where we end up losing more 2.0 users because of a forced Guava jump than we gain from being Guava 20 compatible. To be continued on the dev list, I suspect... ;-) --- 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-232640304
