Thanks all for the quick responses! @andrewgaul Yes Stopwatch constructor has been made private in com.google.guava 17.0. That's the reason why I think we see this problem.
@andreaturli I think I found the problem. I was able to build jclouds-labs master branch without any problem therefore I checked following class there and found: jclouds-labs/virtualbox/src/main/java/org/jclouds/virtualbox/functions/CreateAndInstallVm.java Stopwatch stopwatch = Stopwatch.createUnstarted(); stopwatch.start(); However after applying this pull request on top of the master branch I see the following: jclouds-labs/virtualbox/src/main/java/org/jclouds/virtualbox/functions/CreateAndInstallVm.java Stopwatch stopwatch = new Stopwatch(); stopwatch.start(); I fixed this problem locally and then got the following error: jclouds-labs/fgcp/src/main/java/org/jclouds/fujitsu/fgcp/suppliers/FGCPCredentialsSupplier.java:[82,68] cannot find symbol [ERROR] symbol : method privateKeySpec(org.jclouds.io.payloads.StringPayload) [ERROR] location: class org.jclouds.crypto.Pems I have a quick question: I was able to fix above two issues locally and test this PR. However when I start a Docker container via this jclouds Docker API, the container starts successfully but it exits soon after. This is the same behaviour as we start a container using docker client without specifying -d option to ask docker to detach it. Do you have any thoughts on this? Many Thanks --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/57#issuecomment-45089212
