[jira] [Assigned] (JCLOUDS-704) Unable to create Virtual guest in SoftLayer

[ https://issues.apache.org/jira/browse/JCLOUDS-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignasi Barrera reassigned JCLOUDS-704: -- Assignee: Andrea Turli > Unable to create Virtual guest in SoftLayer > ---

Jenkins build is back to normal : jclouds-labs-openstack #449

See

Jenkins build is back to normal : jclouds-labs-openstack » jclouds openstack-swift api #449

See

Re: [jclouds] JCLOUDS-706: Upgrade Azure API to 2012-02-12 (#508)

[jclouds » jclouds #1596](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1596/) 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.com/jclouds/jcl

Jenkins build is still unstable: jclouds » jclouds #1596

See

[jira] [Commented] (JCLOUDS-641) rackspace-cloudfiles-us integration tests fail

[ https://issues.apache.org/jira/browse/JCLOUDS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14122307#comment-14122307 ] Andrew Gaul commented on JCLOUDS-641: - [~jdaggett] Any updates on this issue? I cons

Re: [jclouds] JCLOUDS-706: Upgrade Azure API to 2012-02-12 (#508)

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

Build failed in Jenkins: jclouds-labs-openstack #448

See -- [...truncated 1476 lines...] [WARNING]

Build failed in Jenkins: jclouds-labs-openstack » jclouds openstack-swift api #448

See -- [INFO] [INFO]

Jenkins build is back to stable : jclouds » jclouds compute core #2741

See

Jenkins build is back to stable : jclouds #2741

See

Jenkins build is still unstable: jclouds » jclouds #1595

See

Re: [jclouds-labs-google] JCLOUDS-458:Added Blobstore Abstraction (#48)

> +import org.jclouds.googlecloudstorage.options.ListObjectOptions; > +import org.jclouds.http.HttpResponseException; > +import org.jclouds.http.internal.PayloadEnclosingImpl; > + > +import com.google.common.base.Charsets; > +import com.google.common.base.Function; > +import com.google.common.base.

Re: [jclouds-labs-google] JCLOUDS-458:Added Blobstore Abstraction (#48)

> +import org.jclouds.googlecloudstorage.options.ListObjectOptions; > +import org.jclouds.http.HttpResponseException; > +import org.jclouds.http.internal.PayloadEnclosingImpl; > + > +import com.google.common.base.Charsets; > +import com.google.common.base.Function; > +import com.google.common.base.

Re: [jclouds] JCLOUDS-706: Upgrade Azure API to 2012-02-12 (#508)

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

Re: [jclouds] JCLOUDS-706: Upgrade Azure API to 2012-02-12 (#508)

Successfully ran integration tests. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/508#issuecomment-54566376

[jclouds] JCLOUDS-706: Upgrade Azure API to 2012-02-12 (#508)

This will allow use of Azure after August 2015: http://blogs.msdn.com/b/windowsazurestorage/archive/2014/08/05/microsoft-azure-storage-service-version-removal.aspx You can merge this Pull Request by running: git pull https://github.com/andrewgaul/jclouds azure-version Or you can view, comment

[jira] [Created] (JCLOUDS-706) Upgrade Azure API version to 2012-02-12

Andrew Gaul created JCLOUDS-706: --- Summary: Upgrade Azure API version to 2012-02-12 Key: JCLOUDS-706 URL: https://issues.apache.org/jira/browse/JCLOUDS-706 Project: jclouds Issue Type: Improveme

Jenkins build became unstable: jclouds » jclouds #1594

See

Re: [jclouds] Remove ByteStreams2.asByteSource (#507)

Pushed to master as 8613967820b3918a8b930f41179205675925f5d6. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/507#issuecomment-54563906

Re: [jclouds] Use try-with-resources where appropriate (#506)

Also agree that we should not change examples until 2.0 releases. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/506#issuecomment-54555176

Re: [jclouds] Use try-with-resources where appropriate (#506)

We could defer merging this until later in the 2.0 cycle to minimize backporting pain. maven-compiler-plugin enforces the correct subset of language features but cannot enforce the correct subset of library interfaces. animal-sniffer-maven-plugin does this library enforcement but I have had po

[jira] [Updated] (JCLOUDS-704) Unable to create Virtual guest in SoftLayer

[ https://issues.apache.org/jira/browse/JCLOUDS-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaiganesh Mathaiyan updated JCLOUDS-704: Description: Error while creating a virtual guest in softlayer 2014-09-04 15:29:45,

[jira] [Created] (JCLOUDS-705) Support OpenStack Swift Storage Policies

Jeremy Daggett created JCLOUDS-705: -- Summary: Support OpenStack Swift Storage Policies Key: JCLOUDS-705 URL: https://issues.apache.org/jira/browse/JCLOUDS-705 Project: jclouds Issue Type: Ne

[jira] [Updated] (JCLOUDS-704) Unable to create Virtual guest in SoftLayer

[ https://issues.apache.org/jira/browse/JCLOUDS-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Phillips updated JCLOUDS-704: Summary: Unable to create Virtual guest in SoftLayer (was: Create Virtual guest throws err

Re: [jclouds-labs-openstack] Cleans up neutron code (#139)

Thanks for the changes, @zack-shoylev! Still a couple of [Checkstyle violations](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/405/violations/), by the way...but they don't seem to be related to this PR..? --- Reply to this email directly or view it on GitHub: https:/

Re: [jclouds-labs-openstack] Cleans up neutron code (#139)

> @@ -40,7 +40,7 @@ public String toString() { >return name; > } > > - /** > was OK here, so why the change? Originally my review comment, @jdaggett ;-) I made it because this seems like a comment for a jclouds-dev, not something a **user** of jclouds would expect in the Javadoc

[jira] [Updated] (JCLOUDS-704) Create Virtual guest throws error

[ https://issues.apache.org/jira/browse/JCLOUDS-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaiganesh Mathaiyan updated JCLOUDS-704: Environment: provider: Softlayer JDK: 1.7 provider/softlayer code deployed from gi

[jira] [Created] (JCLOUDS-704) Create Virtual guest throws error

Jaiganesh Mathaiyan created JCLOUDS-704: --- Summary: Create Virtual guest throws error Key: JCLOUDS-704 URL: https://issues.apache.org/jira/browse/JCLOUDS-704 Project: jclouds Issue Type:

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

> Already deployed it :) I noticed...but we can always apply a little edit here and there if we think that's merited ;-) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54546199

Re: [jclouds] Remove ByteStreams2.asByteSource (#507)

+1 - looks good to me. Can't see if there are any Checkstyle violations due to our hanging MWS test issue...could you kindly run that locally (if not done already) to check? Thanks, @andrewgaul! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/507#i

Re: [jclouds-examples] The start of examples for OpenStack (#62)

Thanks @nacx! Fixed and merged. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-examples/pull/62#issuecomment-54543435

Re: [jclouds] JCLOUDS-686: Remove changesSince() query from base PaginationOptions (#499)

> @@ -44,7 +42,12 @@ public PaginationOptions queryParameters(Multimap String> queryParams) { > > /** > * Only return objects changed since this time. > +* > +* @deprecated The {@code changes-since} query does not apply to all > OpenStack APIs. Please refer to the OpenStack > +

Re: [jclouds] Use try-with-resources where appropriate (#506)

> from here on out will require removing these changes while backporting. > Correct? Yes, I think so. Hopefully we can ensure we submit PRs also for the backports, then the Java 6 builder should start failing horribly if we try to use these constructs. --- Reply to this email directly or view

Re: [jclouds] Use try-with-resources where appropriate (#506)

The MWS test issue is hanging the PR builder :-( ``` Starting test testZeroLengthPutHasContentLengthHeader(org.jclouds.s3.S3ClientMockTest) Sep 04, 2014 12:49:21 AM com.squareup.okhttp.mockwebserver.MockWebServer$3 processOneRequest INFO: Received request: PUT /bucket/object HTTP/1.1 and responde

Re: [jclouds-labs-openstack] Glance API ListImageOptions should support changesSince() (#137)

Pushed to master 9782342 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/137#issuecomment-54510551

Jenkins build became unstable: jclouds » jclouds compute core #2740

See

Jenkins build became unstable: jclouds #2740

See

Re: [jclouds] JCLOUDS-686: Remove changesSince() query from base PaginationOptions (#499)

> @@ -44,7 +42,12 @@ public PaginationOptions queryParameters(Multimap String> queryParams) { > > /** > * Only return objects changed since this time. > +* > +* @deprecated The {@code changes-since} query does not apply to all > OpenStack APIs. Please refer to the OpenStack > +

Re: [jclouds-labs-openstack] Glance API ListImageOptions should support changesSince() (#137)

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

[jira] [Commented] (JCLOUDS-686) Remove OpenStack PaginationOptions.changesSince()

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

Re: [jclouds-labs-openstack] Cleans up neutron code (#139)

Thanks @jdaggett ! I will be sitting on this one for a bit to figure out if we want to rename createOptions/updateOptions. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/139#issuecomment-54509797

Re: [jclouds] Remove ByteStreams2.asByteSource (#507)

[jclouds-pull-requests #1145](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1145/) ABORTED --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/507#issuecomment-54509746

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

Already deployed it :) but will consider adding some more to illustrate the "create for create" example. About fonts: I don't like using that much outside code blocks, but I see what you are saying with regards to consistency. Hmm. --- Reply to this email directly or view it on GitHub: https://g

Re: [jclouds] Use try-with-resources where appropriate (#506)

[jclouds-pull-requests #1143](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1143/) ABORTED --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/506#issuecomment-54509589

Re: [jclouds] Ensure that Content-MD5 has 128 bits (#504)

> jclouds-pull-requests #1139 ABORTED ``` Build timed out due to Global Timeout (after 1440 minutes). Marking the build as aborted. ``` It's that MWS test again :-( --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/504#issuecomment-54509505

Re: [jclouds] Nova API Updates (#505)

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

Re: [jclouds-labs-openstack] Glance API ListImageOptions should support changesSince() (#137)

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

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

Thanks, @zack-shoylev! Great to see more posts on the blog. Just a bunch of minor comments, many of them around code font (or not) for things like classes. I have no strong preference either way, but it would be good to be consistent with other blog posts... --- Reply to this email directly or

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

> +In this case, it was easy to add support for this call by using a [map > binder](https://github.com/jclouds/jclouds/blob/master/apis/openstack-trove/src/main/java/org/jclouds/openstack/trove/v1/binders/BindCreateUserToJson.java). > + > +However, some APIs send or receive significantly more comp

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

> +Some [simpler > classes](https://github.com/jclouds/jclouds-labs-openstack/blob/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2/domain/AddressPair.java) > implement the regular fluent builder pattern. > + > +In [other > cases](https://github.com/jclouds/jclouds-labs-o

Re: [jclouds] Ensure that Content-MD5 has 128 bits (#504)

[jclouds-pull-requests #1139](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1139/) ABORTED --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/504#issuecomment-54508329

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

> + > +We want to > + > +1. Ensure object immutability. > +2. Utilize the fluent builder pattern. > +3. Ensure that "create" objects can only be used for create; update for > update; and listed resources cannot be directly sent back to the service. > +4. Reuse code and keep domain classes > [DRY]

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

> + > +In addition to fixing these issues, jclouds wants to provide developers with > some compiler checks and other syntactic sugar (fluent builders), while also > supporting different updating, creating, or listing validation strategies. > + > +We want to > + > +1. Ensure object immutability. >

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

> +1. Heavy use of map-binders and parsers to transform JSON. Map-binders use > annotation-selected classes to map method data (such as the data in the > create-user call above) to the JSON required by the service. The > [parsers](https://github.com/jclouds/jclouds-labs-openstack/blob/master/op

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

> +Current implementations have the following two issues : > + > +1. Heavy use of map-binders and parsers to transform JSON. Map-binders use > annotation-selected classes to map method data (such as the data in the > create-user call above) to the JSON required by the service. The > [parsers](h

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

> + > +To parse the response, jclouds uses [domain > classes](https://github.com/jclouds/jclouds/blob/master/apis/openstack-trove/src/main/java/org/jclouds/openstack/trove/v1/domain/User.java) > to represent the JSON data returned by the service. The array of "users" is > unwrapped into individu

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

> +} > +] > +} > +{% endhighlight %} > + > +To parse the response, jclouds uses [domain > classes](https://github.com/jclouds/jclouds/blob/master/apis/openstack-trove/src/main/java/org/jclouds/openstack/trove/v1/domain/User.java) > to represent the JSON data returned by the service. T

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

> +{ > +"databases": [ > +{ > +"name": "sampledb" > +} > +], > +"host": "%", > +"name": "demouser" > +} > +] > +} > +{% endhighlight %} > + > +To parse the response, jclouds uses

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

> +"host": "%" > +}, > +{ > +"databases": [ > +{ > +"name": "sampledb" > +} > +], > +"host": "%", > +"name": "demouser" > +} > +] > +} > +{% endhighlight %} >

Re: [jclouds-labs-openstack] OpenStack Heat Support (#138)

@nacx I made your suggested changes, thx! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/138#issuecomment-54504007

Re: [jclouds-labs-openstack] OpenStack Heat Support (#138)

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

Re: [jclouds-labs-openstack] OpenStack Heat Support (#138)

@sharwell In jclouds we refer to the code names for the OpenStack projects in the code. Naming it Heat here keeps it consistent with the rest of the code. In documentation we'll refer to it as both. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-op

Re: [jclouds-labs-openstack] OpenStack Heat Support (#138)

Considering that both OpenStack and Rackspace now refer to this service as "Orchestration", would it make sense to rename this feature for consistency prior to its introduction in jclouds? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pu

Re: [jclouds] Use try-with-resources where appropriate (#506)

Just to be clear, after this merges, any changes to these classes that needs to be backported to 1.8.x from here on out will require removing these changes while backporting. Correct? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/506#issuecomment-

Re: [jclouds] Use try-with-resources where appropriate (#506)

My preference too is to not use any Java 7 specific features in the examples until we've released 2.0.0. The examples really should be consistent with the language level we support. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/506#issuecomment-54

Re: [jclouds-examples] Updated Clojure and jclouds versions (#53)

Closed #53. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-examples/pull/53#event-161258946

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

Closed #124. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/124#event-161253336

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

Website deployed. It seems to not be completely broken so far. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54493351

Re: [jclouds] Use try-with-resources where appropriate (#506)

Yay Java 7! Thanks, @andrewgaul! I was going to make the same comment @nacx made about the examples, but I guess we should only do that when we release a new version that _only_ supports Java 7..? +1 from me too, by the way. --- Reply to this email directly or view it on GitHub: https://github.

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

merged --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54491307

[jira] [Commented] (JCLOUDS-703) Google Hardware no longer supports images

[ https://issues.apache.org/jira/browse/JCLOUDS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121436#comment-14121436 ] Stuart Hendren commented on JCLOUDS-703: There's a relevant TODO in MachineTypeIn

Re: [jclouds-labs-openstack] Cleans up neutron code (#139)

@jdaggett let me know if my comments answer your questions or if there is anything else. Thanks! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/139#issuecomment-54480981

[jira] [Created] (JCLOUDS-703) Google Hardware no longer supports images

Stuart Hendren created JCLOUDS-703: -- Summary: Google Hardware no longer supports images Key: JCLOUDS-703 URL: https://issues.apache.org/jira/browse/JCLOUDS-703 Project: jclouds Issue Type: B

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

Merge and publish! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54484345

Re: [jclouds-labs-openstack] Cleans up neutron code (#139)

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

Re: [jclouds-labs-openstack] Cleans up neutron code (#139)

[jclouds » jclouds-labs-openstack #1674](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-openstack/1674/) 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/jclo

Re: [jclouds] Implemented compute attach interfaces extension. (#497)

No @RoadRoller. The PR is very welcome! I wasn't sure if the expect tests were complete or no and just wanted to leave the note. Thanks! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/497#issuecomment-54479743

Re: [jclouds-labs-openstack] Cleans up neutron code (#139)

> > - Rule newSecGroupRule = null; > - for(Rule sgr : securityGroup.getRules()) { > -if(sgr.getId().equals(rule.getId())) { > - newSecGroupRule = sgr; > - break; > -} > - } > - assertNotNull(newSecGroupRule, "Did

Re: [jclouds] Implemented compute attach interfaces extension. (#497)

@nacx I understand that tests in incomplete, but in this month I'm have no free time to do it. I suppose I return to it work in October. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/497#issuecomment-54473842

Re: [jclouds-labs-openstack] OpenStack Heat Support (#138)

> + test > + > + > + ch.qos.logback > + logback-classic > + test > + > + > + com.squareup.okhttp > + mockwebserver > + test > + > + > + org.yaml > + snakeyaml > + 1.13 I assume this will be needed if we're going to parse the

Re: [jclouds-labs-openstack] OpenStack Heat Support (#138)

> +target/test-data/jclouds.log > + > + > +%d %-5p [%c] [%thread] %m%n > + > + > + > + > +target/test-data/jclouds-wire.log > + > + > +%d %-5p [%c] [%thread] %m%n > + > + > + > + Remove this appender? --- Repl

Re: [jclouds-labs-openstack] OpenStack Heat Support (#138)

> + > + /* > + * Check response > + */ > + assertThat(resourceTypes).isNotEmpty(); > + assertThat(resourceTypes.size()).isEqualTo(20); > + > + } finally { > + server.shutdown(); > + } > + } > + > + public void testListTypesIsEmpty() th

Re: [jclouds] Implemented compute attach interfaces extension. (#497)

> +.method("GET") > +.endpoint( > + > "https://az-1.region-a.geo-1.compute.hpcloudsvc.com/v2/3456/servers/instance-1/os-interface/ce531f90-199f-48c0-816c-13e38010b442";) > +.addHeader("Accept", > "application/json").addHeader("X-Auth-Token", au

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

Alright, problems with the PR build script seem fixed now. This also seems good to merge. Should I merge it? Is there anything else that needs to be done? The front page has a link to the blog I think. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

Go to http://306ae818722ae6b78b92-2e69301a260e5804fbad8c2752c99931.r57.cf5.rackcdn.com/ to review your changes. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54458152

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

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

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

Reopened #124. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/124#event-161132059

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

Closed #124. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/124#event-161132054

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

to review your changes. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54454813

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

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

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

Reopened #124. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/124#event-161122494

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

to review your changes. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54454032

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

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

[jira] [Commented] (JCLOUDS-687) Configurable API/Provider Default Page Size

[ https://issues.apache.org/jira/browse/JCLOUDS-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121233#comment-14121233 ] Andrey Trubitsyn commented on JCLOUDS-687: -- Hi Guys, Thank you for your feedbac

Re: [jclouds] Use try-with-resources where appropriate (#506)

+1. In fact this is something we could also apply to the jclouds context in our examples. This way people won't forget to close the context, leaving the executors running and the program hanging until killed. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclou

Re: [jclouds-examples] The start of examples for OpenStack (#62)

> @@ -0,0 +1,109 @@ > +package org.jclouds.examples.openstack.identity; Add the ASF header --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-examples/pull/62/files#r17104159

Re: [jclouds-examples] The start of examples for OpenStack (#62)

> @@ -0,0 +1,64 @@ > +# Rackspace Examples OpenStack? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-examples/pull/62/files#r17103832

Re: [jclouds-examples] The start of examples for OpenStack (#62)

> +the License. You may obtain a copy of the License at > + > +http://www.apache.org/licenses/LICENSE-2.0 > + > +Unless required by applicable law or agreed to in writing, software > +distributed under the License is distributed on an "AS IS" BASIS, > +WITHOUT WARRANTIES OR