Thanks for the heads-up!

I think both, forwarding to the user list and a post + tweet pointing to
the post? :)
El 24/01/2014 07:18, "Andrew Phillips" <[email protected]> escribió:

> Quick update on the current status of jclouds & Java 7u51:
>
> - The underlying Guava issue [1] is still open, and we're waiting to see
> what happens there before deciding on "the right thing to do"
> - In the meantime, we have found and applied a workaround to master and
> 1.7.x (still working on 1.6.x)
> - If you're currently using jclouds, your options are:
>
> 1. Do *not* upgrade to 7u51 for the time being, if you can avoid it. Stick
> with 7u45 or earlier Java versions. This will allow you to keep using
> jclouds just the way you are doing so far.
> 2. If you can't avoid 7u51, use the latest snapshot version for your
> branch, i.e. 1.8.0-SNAPSHOT, 1.7.1-SNAPSHOT (still working on
> 1.6.3-SNAPSHOT). How to get hold of jclouds snapshots builds is described
> on the jclouds site [2]. Snapshots with the patch should be appearing in
> the Apache snapshot repo about now, but you can verify whether the snapshot
> JAR you've downloaded contains the workaround by looking for the TypeToken2
> class:
>
> $ jar -tvf jclouds-core-<version>.jar org/jclouds/util/TypeToken2.class
>   3944 Thu Jan 23 23:38:00 EST 2014 org/jclouds/util/TypeToken2.class
>
> - The plan for now from the jclouds side is: give the Guava team a week or
> two to react to this. We want to get a released version of jclouds working
> on the latest Java version as quickly as possible too, rest assured ;-)
> - Whichever way the decision goes, the next 1.6.x and 1.7.x releases will
> work on the latest Java version!
>
> Is something like this OK to post on the user list? Or rather in a blog?
> Or..?
>
> Regards
>
> ap
>
> [1] https://code.google.com/p/guava-libraries/issues/detail?id=1635
> [2] http://jclouds.apache.org/documentation/userguide/
> installation-guide/#snapshot
>

Reply via email to