> If a 1.6.4 release is not planned why does this issue have it marked as such in its "Fixed Version/s"
Fair point. I suspect it was set because the issue should be resolved in the current 1.6.x branch, the next release of which would be 1.6.4. Similarly, 1.8.0 has not been released yet, but that will be the version in which the issue will be fixed on trunk.
If you cannot upgrade to Guava 16 to use jclouds 1.7.1, could you send an email to the user list  to help us gauge how many users are in a similar situation? That will make it easier to decide on the priority of a 1.6.4 release.