Jenkins build is still unstable: jclouds » jclouds-karaf #1404

See

Re: [jclouds] Accidentally set limited json fallback field naming to an enum. (#589)

[jclouds-pull-requests #1357](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1357/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/589#issuecomment-60715975

Re: [jclouds] Accidentally set limited json fallback field naming to an enum. (#589)

[jclouds-pull-requests-java-7 #268](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests-java-7/268/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/589#issuecomment-60715524

Re: [jclouds-labs] Add vSphere support (#61)

[jclouds » jclouds-labs #1809](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1809/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pul

Re: [jclouds] Accidentally set limited json fallback field naming to an enum. (#589)

cc @nacx @zack-shoylev @andreaturli This change will allow us to not need `@SerializedName` in most cases. watch for an example on https://github.com/jclouds/jclouds-labs/pull/102 soon. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/589#issuecommen

Re: [jclouds] Accidentally set limited json fallback field naming to an enum. (#589)

> @@ -16,6 +16,45 @@ > */ > package org.jclouds.json.config; > > +import static com.google.common.io.BaseEncoding.base16; forgive me.. I couldn't help reformatting imports. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/589/files#r19454722

[jclouds] Accidentally set limited json fallback field naming to an enum. (#589)

In docker, I need to set a custom field naming policy that isn't in the enum, as certain names are not normal case. Ex. IP not Ip. You can merge this Pull Request by running: git pull https://github.com/adriancole/jclouds adrian.whoops-too-tight Or you can view, comment on it, or merge it onli

Re: [jclouds-labs] Add vSphere support (#61)

[jclouds-labs-pull-requests #358](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/358/) FAILURE Looks like there's a problem with this pull request --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-60713845

Re: [jclouds-labs] JCLOUDS-750 Start using AutoValue on Docker. (#102)

[jclouds » jclouds-labs #1808](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1808/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pul

[jira] [Commented] (JCLOUDS-737) Docker bindings needs upgrade to Docker API 1.4

[ https://issues.apache.org/jira/browse/JCLOUDS-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14186430#comment-14186430 ] Andrea Turli commented on JCLOUDS-737: -- I've a branch with the needed updates, need

Re: [jclouds-labs] JCLOUDS-750 Start using AutoValue on Docker. (#102)

[jclouds-labs-pull-requests #357](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/357/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/102#issuecomment-60713237

[jira] [Commented] (JCLOUDS-737) Docker bindings needs upgrade to Docker API 1.4

[ https://issues.apache.org/jira/browse/JCLOUDS-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14186413#comment-14186413 ] Adrian Cole commented on JCLOUDS-737: - agreed this needs to be updated. I will be mer

Re: [jclouds-labs-openstack] OS Ceilometer API support (#166)

> + public int hashCode() { > + return Objects.hashCode(userId, name, resourceId, source, meterId, > projectId, type, unit); > + } > + > + protected Objects.ToStringHelper string() { > + return Objects.toStringHelper(this) > +.add("userId", userId).add("name", name).add

Re: [jclouds-labs-openstack] OS Ceilometer API support (#166)

> + > +/** > + * Provides access to the OpenStack Orchestration (Heat) API. > + * > + */ > +public interface CeilometerApi extends Closeable { > + > + @Provides > + @Region > + Set getConfiguredRegions(); > + > + /** > +* Provides access to Meters features. > +*/ > + @Delegate > +

Re: [jclouds-labs-openstack] OS Ceilometer API support (#166)

> + .credentialName("${password}") > + > .documentation(URI.create("https://wiki.openstack.org/wiki/Ceilometer";)) > + .version("2") > + .endpointName("Keystone base url ending in /v2.0/") > + .defaultEndpoint("http://localhost:5000/v2.0/";) > + > .

Re: [jclouds-labs-openstack] OS Ceilometer API support (#166)

> +jclouds components to access an implementation of OpenStack > Ceilometer > +bundle > + > + > + > + > http://localhost:5000/v2.0/ > + > 1 > + > + > FIXME_IDENTITY > + > FIXME_CREDENTIALS > + > passwordCredentials > + > o

Re: [jclouds-labs-openstack] OS Ceilometer API support (#166)

> +import java.util.Set; > + > +import org.jclouds.location.Region; > +import org.jclouds.location.functions.RegionToEndpoint; > +import org.jclouds.openstack.ceilometer.v2.features.MetersApi; > +import org.jclouds.openstack.ceilometer.v2.features.QueryApi; > +import org.jclouds.rest.annotations.De

Jenkins build is still unstable: jclouds » jclouds-karaf #1403

See

Re: [jclouds-karaf] Added the CloudSigma2 providers (#58)

[jclouds » jclouds-karaf #1403](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-karaf/1403/) UNSTABLE Looks like there's a problem with this pull request [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.co

Re: [jclouds-labs] JCLOUDS-750 Start using AutoValue on Docker. (#102)

> @Override > protected void configure() { > + > bind(FieldNamingPolicy.class).toInstance(FieldNamingPolicy.UPPER_CAMEL_CASE); @nacx in the future, when serializednames is used for serialization, too, the above will be redundant. --- Reply to this email directly or view it on GitHu

Re: [jclouds-labs] JCLOUDS-750 Start using AutoValue on Docker. (#102)

> private final List onBuild; > > - > - @ConstructorProperties({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", > + @SerializedNames({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", @nacx fyi I'll update

Re: [jclouds-labs] JCLOUDS-750 Start using AutoValue on Docker. (#102)

> private final List onBuild; > > - > - @ConstructorProperties({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", > + @SerializedNames({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", Can you prove that by

Re: [jclouds-labs] JCLOUDS-750 Start using AutoValue on Docker. (#102)

> private final List onBuild; > > - > - @ConstructorProperties({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", > + @SerializedNames({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", yeah the field names s

Re: [jclouds-labs] JCLOUDS-750 Start using AutoValue on Docker. (#102)

> private final List onBuild; > > - > - @ConstructorProperties({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", > + @SerializedNames({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", It seems the naming wa

Re: [jclouds-labs] JCLOUDS-750 Start using AutoValue on Docker. (#102)

> private final List onBuild; > > - > - @ConstructorProperties({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", > + @SerializedNames({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", Docker APIs contain so

Jenkins build is unstable: jclouds » jclouds-karaf #1402

See

Re: [jclouds-karaf] Added the CloudSigma2 providers (#58)

[jclouds » jclouds-karaf #1402](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-karaf/1402/) UNSTABLE Looks like there's a problem with this pull request [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.co

Re: [jclouds-labs] JCLOUDS-750 Start using AutoValue on Docker. (#102)

> private final List onBuild; > > - > - @ConstructorProperties({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", > + @SerializedNames({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", Hmmm Will it work for

Re: [jclouds-labs] Use guava.version property and otherwise inherit deps for jclouds-management and jclouds-representations. (eea1bdb)

No problem --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/commit/eea1bdb45c271de6a72fd368f485f046287af1eb#commitcomment-8323374

Re: [jclouds-labs] Use guava.version property and otherwise inherit deps for jclouds-management and jclouds-representations. (eea1bdb)

Thanks for that! The task of going through Guava deps in downstream repos was still somewhere on my plate, just hadn't been able to get round to it :-( --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/commit/eea1bdb45c271de6a72fd368f485f046287af1eb#co

Re: [jclouds-labs] JCLOUDS-750 Start using AutoValue on Docker. (#102)

> private final List onBuild; > > - > - @ConstructorProperties({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", > + @SerializedNames({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", Serialization is cover

Re: [jclouds-karaf] Added the CloudSigma2 providers (#58)

[jclouds-karaf-pull-requests #98](https://jclouds.ci.cloudbees.com/job/jclouds-karaf-pull-requests/98/) UNSTABLE Looks like there's a problem with this pull request --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-karaf/pull/58#issuecomment-60686542

Jenkins build is back to normal : jclouds-labs-google » Apache jclouds labs google #288

See

Re: [jclouds-karaf] Added the CloudSigma2 providers (#58)

Hmmm Looking at the test failures, the new CloudSigma tests passed but Chef and others failed. The jclouds build just populated the latest snapshots, so I'll give it another try... --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-karaf/pull/58#issuecommen

Jenkins build is back to normal : jclouds-labs-google #288

See

Re: [jclouds-karaf] Added the CloudSigma2 providers (#58)

Closed #58. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-karaf/pull/58#event-184396378

Re: [jclouds-karaf] Added the CloudSigma2 providers (#58)

Reopened #58. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-karaf/pull/58#event-184396386

Jenkins build is back to normal : jclouds » Apache jclouds Project #2831

See

Jenkins build is back to normal : jclouds #2831

See

Re: [jclouds-karaf] Added the CloudSigma2 providers (#58)

[jclouds-karaf-pull-requests #97](https://jclouds.ci.cloudbees.com/job/jclouds-karaf-pull-requests/97/) UNSTABLE Looks like there's a problem with this pull request --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-karaf/pull/58#issuecomment-60684662

Re: [jclouds-karaf] Added the CloudSigma2 providers (#58)

CloudSigma snapshots should be now in place. Retrying... --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-karaf/pull/58#issuecomment-60682902

Re: [jclouds-karaf] Added the CloudSigma2 providers (#58)

Closed #58. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-karaf/pull/58#event-184388425

Jenkins build is back to normal : jclouds-labs » Apache jclouds labs #645

See

Jenkins build is back to normal : jclouds-labs #645

See

Re: [jclouds-labs] JCLOUDS-750 Start using AutoValue on Docker. (#102)

> private final List onBuild; > > - > - @ConstructorProperties({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", > + @SerializedNames({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", Out of curiosity. Is t

Re: [jclouds-karaf] Added the CloudSigma2 providers (#58)

[jclouds-karaf-pull-requests #96](https://jclouds.ci.cloudbees.com/job/jclouds-karaf-pull-requests/96/) FAILURE Looks like there's a problem with this pull request --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-karaf/pull/58#issuecomment-60677499

Re: [jclouds-karaf] Added the CloudSigma2 providers (#58)

[jclouds » jclouds-karaf #1401](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-karaf/1401/) FAILURE Looks like there's a problem with this pull request [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com

Build failed in Jenkins: jclouds » jclouds-karaf #1401

See Changes: [Ignasi Barrera] Added CloudSigma2 providers -- [...truncated 1289 lines...] [INFO] Copying bundle: org.apache.jclouds.driver:jclouds-log4j:jar:2.0.0-SNAPSHOT [INFO]

[jclouds-karaf] Added the CloudSigma2 providers (#58)

You can merge this Pull Request by running: git pull https://github.com/nacx/jclouds-karaf cloudsigma Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds-karaf/pull/58 -- Commit Summary -- * Added CloudSigma2 providers -- File Changes -- M fea

Re: [jclouds-labs-openstack] OS Ceilometer API support (#166)

Thanks for the contribution @avibh! I am going to start reviewing this PR this afternoon. I am not sure if you are aware of some changes being made to greatly simplify development of new APIs/providers in jclouds with a library called AutoValue. Since we are in a bit of flux there, I would re

Re: [jclouds-labs] JCLOUDS-750 Start using AutoValue on Docker. (#102)

> private final List onBuild; > > - > - @ConstructorProperties({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", > + @SerializedNames({ "Hostname", "Domainname", "User", "Memory", > "MemorySwap", "CpuShares", "AttachStdin", @gk5885 @eamonnmcmanus

Re: [jclouds-labs-google] At the cost of fiddling with type hierarchy adapters, remove lots of junk with google auto (#67)

@gk5885 @eamonnmcmanus @cgruber fyi, another several hundred lines saved thanks to auto. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/67#issuecomment-60667576

Re: [jclouds-labs-google] initial commit to support GCE LB (#22)

> @@ -0,0 +1,12 @@ > +{ > +"kind": "compute#forwardingRule", > +"id": "6732523704970219884", > +"creationTimestamp": "2014-01-08T06:51:10.809-08:00", > +"name": "test-forwarding-rule", > +"region": > "https://www.googleapis.com/compute/v1/projects/myproject/regions/europe-west1";, > +"IPAddress":

Jenkins build is back to normal : jclouds » jclouds-chef #1515

See

[jira] [Commented] (JCLOUDS-759) Make it easier to configure TLS overrides in apache hc driver

[ https://issues.apache.org/jira/browse/JCLOUDS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185592#comment-14185592 ] Andrew Phillips commented on JCLOUDS-759: - Thanks for digging. Pity there doesn't

Build failed in Jenkins: jclouds » jclouds-labs-openstack #1919

See -- Started by upstream project "jclouds/jclouds" build number 1872 originally caused by: GitHub pull request #588 to jclouds/jclouds GitHub pull request #588 to jclouds/jcl

Re: [jclouds] Revert requiring guava 17 (#588)

[jclouds » jclouds #1872](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1872/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/588#issuecomme

Jenkins build is back to normal : jclouds » jclouds-labs #1806

See

Build failed in Jenkins: jclouds-labs-1.8.x-branch » Apache jclouds :: Azure :: Compute API #61

See -- [...truncated 281 lines...] INFO: Received request: GET /services/hostedservices/myservice/deployments/mydeployment HTTP/1.1 and responded: HT

Build failed in Jenkins: jclouds-labs-1.8.x-branch #61

See Changes: [Ignasi Barrera] JCLOUDS-292: Added CloudSigma2 ComputeService -- [...truncated 849 lines...] [Unloading class com.google.common.collect.ImmutableAsList] [Unloading cl

Build failed in Jenkins: jclouds » jclouds-chef #1514

See -- [...truncated 861 lines...] [INFO] Downloading: http://repository.apache.org/snapshots/org/apache/jclouds/provider/elastichosts-sat-p/2.0.0-SNAPSHOT/elastichosts-sat-p-2.0.0-2014102

Build failed in Jenkins: jclouds-labs » Apache jclouds labs #644

See -- [...truncated 2298 lines...] [WARNING] http://community.abiquo.com/display/ABI20/API+Reference" [WARNING]

Build failed in Jenkins: jclouds-labs #644

See Changes: [Ignasi Barrera] JCLOUDS-292: Added CloudSigma2 ComputeService -- [...truncated 2497 lines...] [WARNING]

Re: [jclouds-labs] Add vSphere support (#61)

[jclouds » jclouds-labs #1804](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1804/) ABORTED [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-60637019

Re: [jclouds-labs] Revert requiring guava 17 (#104)

[jclouds » jclouds-labs #1805](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1805/) FAILURE Looks like there's a problem with this pull request [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/j

Build failed in Jenkins: jclouds » jclouds-labs #1805

See -- GitHub pull request #104 to jclouds/jclouds-labs Building remotely on s-2741de28 in workspace Fetching changes fro

Re: [jclouds-labs] CloudSigma2 ComputeService and SecurityGroupExtension (#70)

Closed #70. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/70#event-184207626

Re: [jclouds-labs] CloudSigma2 ComputeService and SecurityGroupExtension (#70)

Rebased and pushed to [master](https://git-wip-us.apache.org/repos/asf?p=jclouds-labs.git;a=commit;h=a7dd1933d8ca283e1118b538be8aa2e2ac5e8be7) and [1.8.x](https://git-wip-us.apache.org/repos/asf?p=jclouds-labs.git;a=commit;h=4c7c29897a2d4f8160a7f14bc0e4d575ccfec882) (after fixing the versions t

[jira] [Resolved] (JCLOUDS-292) Add the ComputeService integration for CloudSigma v2

[ https://issues.apache.org/jira/browse/JCLOUDS-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignasi Barrera resolved JCLOUDS-292. Resolution: Fixed Fix Version/s: 1.8.2 > Add the ComputeService integration for Clou

[jira] [Commented] (JCLOUDS-292) Add the ComputeService integration for CloudSigma v2

[ https://issues.apache.org/jira/browse/JCLOUDS-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185461#comment-14185461 ] ASF subversion and git services commented on JCLOUDS-292: - Commit

[jira] [Commented] (JCLOUDS-292) Add the ComputeService integration for CloudSigma v2

[ https://issues.apache.org/jira/browse/JCLOUDS-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185456#comment-14185456 ] ASF subversion and git services commented on JCLOUDS-292: - Commit

Jenkins build is back to stable : jclouds » jclouds #1871

See

Build failed in Jenkins: jclouds-labs-google » Apache jclouds labs google #287

See -- [...truncated 180 lines...] Downloaded: https://oss.sonatype.org/content/repositories/snapshots/net/schmizz/sshj/maven-metadata.xml (398 B a

Re: [jclouds] Revert requiring guava 17 (#588)

[jclouds-pull-requests #1356](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1356/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/588#issuecomment-60626252

Build failed in Jenkins: jclouds-labs-google #287

See Changes: [Adrian Cole] JCLOUDS-750 At the cost of fiddling with type hierarchy adapters, remove lots of junk with google auto. -- [...truncated 336 lines...] [WARNING]

Re: [jclouds] Revert requiring guava 17 (#588)

[jclouds-pull-requests-java-7 #267](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests-java-7/267/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/588#issuecomment-60625385

Re: [jclouds-labs-aws] Revert requiring guava 17 (#62)

[jclouds » jclouds-labs-aws #1533](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-aws/1533/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-

Re: [jclouds] Revert requiring guava 17 (#588)

[jclouds-pull-requests #1355](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1355/) UNSTABLE Looks like there's a problem with this pull request --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/588#issuecomment-60624591

Re: [jclouds-labs] JCLOUDS-758 Drop VirtualBox labs provider. (#99)

Closed #99. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/99#event-184170505

Re: [jclouds-labs] JCLOUDS-758 Drop VirtualBox labs provider. (#99)

cherry-picked into master, 1.8.x --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/99#issuecomment-60624234

Re: [jclouds-labs-aws] Revert requiring guava 17 (#62)

[jclouds-labs-aws-pull-requests #129](https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws-pull-requests/129/) FAILURE Looks like there's a problem with this pull request --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-aws/pull/62#issuecomment-6062

[jira] [Commented] (JCLOUDS-758) Drop virtualbox labs provider

[ https://issues.apache.org/jira/browse/JCLOUDS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185344#comment-14185344 ] ASF subversion and git services commented on JCLOUDS-758: - Commit

[jira] [Resolved] (JCLOUDS-758) Drop virtualbox labs provider

[ https://issues.apache.org/jira/browse/JCLOUDS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Cole resolved JCLOUDS-758. - Resolution: Fixed > Drop virtualbox labs provider > - > >

[jira] [Commented] (JCLOUDS-758) Drop virtualbox labs provider

[ https://issues.apache.org/jira/browse/JCLOUDS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185341#comment-14185341 ] ASF subversion and git services commented on JCLOUDS-758: - Commit

Re: [jclouds] Revert requiring guava 17 (#588)

> @@ -76,7 +76,7 @@ public boolean apply(@Nullable StorageMetadata input) { > > SocketOpen socketOpen = > context.utils().injector().getInstance(SocketOpen.class); > Predicate socketTester = retry(socketOpen, 1200, 10, > SECONDS); > - > assertTrue(socketTester.apply

Re: [jclouds] Revert requiring guava 17 (#588)

>try { > - Closeables.close(closeable, true); > - } catch (IOException e) { > - throw Throwables.propagate(e); ps. this wasn't possible!! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/588/files#r19417014

Build failed in Jenkins: jclouds-labs-google-1.8.x-branch #63

See Changes: [Adrian Cole] JCLOUDS-750 At the cost of fiddling with type hierarchy adapters, remove lots of junk with google auto. -- Started by an SCM change Building rem

Re: [jclouds-labs-google] At the cost of fiddling with type hierarchy adapters, remove lots of junk with google auto (#67)

cherry-picked into master, 1.8.x --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/67#issuecomment-60622812

Re: [jclouds-labs-google] At the cost of fiddling with type hierarchy adapters, remove lots of junk with google auto (#67)

Closed #67. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/67#event-184165194

[jira] [Commented] (JCLOUDS-750) Replace hand-written domain classes with Auto-Value ones

[ https://issues.apache.org/jira/browse/JCLOUDS-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185323#comment-14185323 ] ASF subversion and git services commented on JCLOUDS-750: - Commit

[jira] [Commented] (JCLOUDS-750) Replace hand-written domain classes with Auto-Value ones

[ https://issues.apache.org/jira/browse/JCLOUDS-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185320#comment-14185320 ] ASF subversion and git services commented on JCLOUDS-750: - Commit

Build failed in Jenkins: jclouds-1.8.x-branch #51

See Changes: [Ignasi Barrera] JCLOUDS-761: Delete disk if image operation fails in ElasticStack -- [...truncated 273 lines...] [INFO] jclouds Amazon Simple Queue Service provider .

Re: [jclouds-labs] Revert requiring guava 17 (#104)

[jclouds-labs-pull-requests #356](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/356/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/104#issuecomment-60621446

Build failed in Jenkins: jclouds-1.8.x-branch » Apache jclouds Project #51

See -- [INFO] [INFO]

Re: [jclouds] JCLOUDS-761: Delete disk if imageDrive operation fails in ElasticStack (#587)

Squashed and pushed to [master](https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=c73ed64fd021fb64e2c7be7f00c2e3248ea5cc0f) and [1.8.x](https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=1df36e733d458a89bcefabf02cc45cfc47ee1fda). --- Reply to this email directly or

Re: [jclouds] Revert requiring guava 17 (#588)

[jclouds-pull-requests-java-7 #266](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests-java-7/266/) FAILURE Looks like there's a problem with this pull request --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/588#issuecomment-60620989

[jira] [Commented] (JCLOUDS-534) Upgrade to Guava 17

[ https://issues.apache.org/jira/browse/JCLOUDS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185305#comment-14185305 ] Adrian Cole commented on JCLOUDS-534: - This change could have been avoided entirely w

[jclouds-labs-aws] Revert requiring guava 17 (#62)

see https://issues.apache.org/jira/browse/JCLOUDS-534 for discussion You can merge this Pull Request by running: git pull https://github.com/adriancole/jclouds-labs-aws adrian.less-guava-incompatibility Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jcloud

[jclouds-labs] Revert requiring guava 17 (#104)

see https://issues.apache.org/jira/browse/JCLOUDS-534 for discussion You can merge this Pull Request by running: git pull https://github.com/adriancole/jclouds-labs adrian.less-guava-incompatibility Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds-la

[jclouds] Revert requiring guava 17 (#588)

see https://issues.apache.org/jira/browse/JCLOUDS-534 for discussion You can merge this Pull Request by running: git pull https://github.com/adriancole/jclouds adrian.less-guava-incompatibility Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/58

  1   2   >