Hi all
If you have been following JCLOUDS-427 [1] you'll around know this,
but otherwise an important message: the current latest released
versions of jclouds (1.7.0 and 1.6.3) do *not* work on Oracle and
OpenJDK version 1.7.0_51 (7u51).
Some status updates:
- The underlying Guava issue [2] 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 or 1.7.1-SNAPSHOT (still working on
1.6.4-SNAPSHOT). How to get hold of jclouds snapshots builds is described
on the jclouds site [3]. Snapshots with the patch should be appearing in
the Apache snapshot repo by 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.
Regards
ap
[1] https://issues.apache.org/jira/browse/JCLOUDS-427
[2] https://code.google.com/p/guava-libraries/issues/detail?id=1635
[3] http://jclouds.apache.org/documentation/userguide/
installation-guide/#snapshot
