Hi, after a little of investigation, it's look like that I can reproduce this bug only when running integration tests with jacoco coverage agent enabled (that was the reason why I cannot reproduce on IDE nor on production, but only when running integration tests under jenkins).
So this is probably a specific issue within GSON and the jacoco bytecode instrumentation. I've tried upgrading GSON to 2.4 and jacoco to 0.7.5.201505241946, anything changed. Not jclouds fault, I will try to report this upstream. Thanks! -- Giovanni Toraldo Lead Developer https://cloudesire.com
