[
https://issues.apache.org/jira/browse/JCLOUDS-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182402#comment-14182402
]
Adrian Cole edited comment on JCLOUDS-653 at 10/24/14 3:58 AM:
---------------------------------------------------------------
[~andrewp] FYI I have corrected all the modules that have blatant only guava 18
compatibility. I'm not sure that this is everything, but a good start. The
above pull requests will rot fast, so any help you can do with regards to
supporting this revert will be welcome.
Note that this is a big part of future backports to 1.8.x being easy as well.
That said the primary reason is to not have a guava version policy of only that
one that just came out.. screw all else.
was (Author: adriancole):
[~andrewp] FYI I have corrected all the modules that have blatant guava 18
compatibility. I'm not sure that this is everything, but a good start. The
above pull requests will rot fast, so any help you can do with regards to
supporting this revert will be welcome.
Note that this is a big part of future backports to 1.8.x being easy as well.
That said the primary reason is to not have a guava version policy of only that
one that just came out.. screw all else.
> Upgrade to Guava 18
> -------------------
>
> Key: JCLOUDS-653
> URL: https://issues.apache.org/jira/browse/JCLOUDS-653
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
> Affects Versions: 2.0.0
> Reporter: Andrew Gaul
> Assignee: Adrian Cole
> Fix For: 2.0.0
>
>
> Notably this release continues the transition from InputSupplier to
> ByteSource and adds a CRC32C implementation, needed by Google Cloud Storage.
> Release notes:
> https://code.google.com/p/guava-libraries/wiki/Release18
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
