[
https://issues.apache.org/jira/browse/JCLOUDS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065517#comment-14065517
]
Aled Sage commented on JCLOUDS-622:
-----------------------------------
Is deleting `Strings2.toString(InputSupplier)` rather than deprecating it too
aggressive? 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
> Guava 18 compatibility
> ----------------------
>
> Key: JCLOUDS-622
> URL: https://issues.apache.org/jira/browse/JCLOUDS-622
> Project: jclouds
> Issue Type: Bug
> Affects Versions: 1.8.0
> Reporter: Andrew Gaul
> Assignee: Andrew Gaul
>
> Guava 16 deprecated and Guava 18 will remove many InputSupplier methods that
> jclouds relies on. jclouds should use alternate methods to allow users to
> upgrade to Guava 18 when Google releases it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
