Relating more to the already-merged commit https://github.com/jclouds/jclouds/commit/fb60d76704745317186ad700e9b7ce5a569a614d, and as commented on in the JCLOUDS-622 issue ...
Is deleting `Strings2.toString(InputSupplier)` rather than deprecating it too aggressive for 1.8? Though guava 18 will delete methods using `InputSupplier`, the interface will stick around until either June or December 2015 [1,2]. So we can deprecate toString(InputSupplier) in 1.8 and delete it in jclouds 1.9, as per the jclouds deprecation policy? See https://github.com/jclouds/jclouds-labs/pull/69 for downstream fixes to remove usage of this method. [1] https://code.google.com/p/guava-libraries/wiki/Release16 [2] http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/io/InputSupplier.html --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/438#issuecomment-49369341
