Just want to know if someone knows the reason for that configuration
being there. There is no need to remove it at all. I just want to make
sure that configuration is there for a reason, not just because it
was already there :)
I suspect it might be one of those reasons lost in the dawn of
Looks good to me - squash'n'rebase? Thanks, @zack-shoylev!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/67#issuecomment-30932265
I notice we're also releasing jclouds-labs-aws and jclouds-labs-google
this time, as per the updated release instructions [1]. Do we also
need to update the sample email there (or add a different one for
1.7.x)?
ap
[1] https://wiki.apache.org/jclouds/Releasing%20jclouds
You can merge this Pull Request by running:
git pull https://github.com/jclouds/jclouds-labs-openstack remove-header-file
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-labs-openstack/pull/70
-- Commit Summary --
* JCLOUDS-411: Removing
You can merge this Pull Request by running:
git pull https://github.com/jclouds/jclouds-labs-google remove-header-file
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-labs-google/pull/18
-- Commit Summary --
* JCLOUDS-411: Removing unneeded
Open to cut another RC to incorporate the Rackspace changes - whatever
the RM decides ;-) As for this candidate...
===
Apache ID: andrewp
---
[X] +1 Release.
Both commits are already in 1.7.x [1] [2]
Just out of interest: wouldn't these have caused a merge conflict for
abayer when trying to push the release commits? I guess we should not
be touching the release branch until the release commits are
published, no..?
ap
No, I want the changes in 1.7.x - I'll nuke the existing release-process
commits and replace them with new ones.
Sorry, yes, I should have added that this won't be a problem if we're
going to cut new RCs. I was just thinking that, in general, we should
be considering the release branch
Source and binary files:
https://dist.apache.org/repos/dist/dev/jclouds/jclouds-1.7.0-rc2
Link is wrong? This seems to be the right place:
https://dist.apache.org/repos/dist/dev/jclouds/1.7.0-rc2/
ap
@timur87 Review might take a bit this time. We're a bit tied up with the 1.7.0
release right now, so thanks for your patience... ;-)
Let me close'n'reopen to at least trigger a new PR build.
---
Reply to this email directly or view it on GitHub:
+ groupIdorg.apache.jclouds.labs/groupId
+ artifactIdorion/artifactId
+ nameorion-blobstore/name
+ descriptionjclouds components to access Orion as a
blobstore/description
+ packagingbundle/packaging
+
+ scm
+
Release itself looks good so far. But how does the thing with the tags
and the dist link work? Do we need another [VOTE] email, or is this
update sufficient..?
ap
jclouds-java-7-pull-requests #952 UNSTABLE
Unrelated [test
failure](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/org.apache.jclouds$jclouds-compute/952/testReport/junit/org.jclouds.compute.util/ConcurrentOpenSocketFinderTest/testChecksSocketsConcurrently/).
Looks like a
I minimized this commit so that we can backport to 1.7.x
Definitely +1 on this approach - was more curious about where we go from here
in 1.8.x...
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/241#issuecomment-31051994
I suspect ef82667 is also the reason why the NOTICE file for Chef looks like
```
Copyright 2013 The Apache Software Foundation
```
vs.
```
Copyright 2009-2013 The Apache Software Foundation
```
for the [other
projects](https://github.com/jclouds/jclouds/blob/master/project/pom.xml#L34)
You can
With regard to the slight difference in the NOTICE file of
jclouds-chef vs. the other projects, I think that should hopefully be
fixed by:
https://github.com/jclouds/jclouds-chef/pull/39
ap
I found some issues with Guava 16.0-rc1 and reported them in
JCLOUDS-415. We should not hold up 1.7.0 for this but definitely
address it in 1.7.1.
Is there something we need to add to the release notes to help people
with potential Guava-related issues in 1.7.0?
ap
I do not believe users can combine Guava 16 and jclouds 1.7.0.
Unfortunately we did not address the deprecation warnings despite the
generous notice.
Would Note: jclouds 1.7.0 is incompatible with Guava 16. Please
switch to Guava 15.0 or earlier, or wait for jclouds 1.7.1 sound
about
The update is sufficient, I believe.
OK, thanks! In that case:
===
Apache ID: andrewp
---
[X] +1 Release.
[ ] -1 Don't release (see notes).
jclouds » jclouds-karaf #634 FAILURE
Not much detail, unfortunately, beyond:
```
cause : Compilation failure
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:testCompile
(default-testCompile) on
@abayer @nacx: Could either of you have a quick look at this? Thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/28#issuecomment-31072431
jclouds » jclouds-labs #702 FAILURE
```
[ERROR] COMPILATION ERROR :
[ERROR]
/scratch/jenkins/workspace/jclouds/jclouds-labs/virtualbox/src/main/java/org/jclouds/virtualbox/functions/admin/FileDownloadFromURI.java:[21,31]
cannot find symbol
symbol: class Closeables2
location: package
@andrewgaul Rebase or close?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/44#issuecomment-31168470
Tada - they're set up with 1.7.1-SNAPSHOT versions. I'm kicking builds
through on dev@cloud now to get the SNAPSHOTs deployed.
DEV@cloud lookin' good...thanks for pushing through the release, abayer!
ap
The full change log is available here:
https://issues.apache.org/jira/browse/JCLOUDS/fixforversion/12324405
For some reason, this contains much less information than
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324405styleName=HtmlprojectId=12314430
..?
ap
Please wait with merging: Javadoc for 1.7.0 still being built...
You can merge this Pull Request by running:
git pull https://github.com/jclouds/jclouds-site 1.7.0-rel-notes
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/44
-- Commit
{% endhighlight %}
## a id=lib/aMaking your own lib dir
* Using maven:
-* Create a pom.xml file with dependencies you need (ex.
org.apache.jclouds/jclouds-all) and the snapshot repository, if you want
snapshot version (1.6.4-SNAPSHOT).
+* Create a pom.xml file with
Anyone up for writing a blog about 1.7.0? Main things would be
de-async (and future plans around that) and ApiConext/buildApi, I
guess? As well as graduation of some projects from labs?
ap
+0, due to vote prematurely closing. The failures against Amazon EC2
concern me and some compute contributor should investigate. Across the
board blobstores tested cleanly although when running integration tests
I encountered symptoms of JCLOUDS-305 against Amazon S3 and JCLOUDS-342
against
@@ -71,6 +71,11 @@ The [clouddatabases
package](https://github.com/jclouds/jclouds-examples/tree/ma
*
[TestDatabase.java](https://github.com/jclouds/jclouds-examples/blob/master/rackspace/src/main/java/org/jclouds/examples/rackspace/clouddatabases/TestDatabase.java)
- An example of
+import static
org.jclouds.examples.rackspace.cloudqueues.Constants.NUM_THREADS;
+import static
org.jclouds.examples.rackspace.cloudqueues.Constants.PRODUCER_ID;
+import static
org.jclouds.examples.rackspace.cloudqueues.Constants.PRODUCER_NAME;
+import static
+ // To use the Rackspace Cloud (UK) set the system property or default
value to rackspace-cloudqueues-uk
+ public static final String PROVIDER = System.getProperty(provider.cbs,
rackspace-cloudqueues-us);
+ public static final String ZONE = System.getProperty(zone, IAD);
+
+
+ private final MessageApi messageApi;
+
+ protected Producer(String producerName) {
+ this.producerName = producerName;
+ messageApi = marconiApi.getMessageApiForZoneAndClientAndQueue(ZONE,
PRODUCER_ID, NAME);
+ }
+
+ public void run() {
+
+
+messageApi.deleteByClaim(message.getId(),
message.getClaimId().get());
+ }
+ }
+
+ private Properties loadStringProperties(String body) {
+ Properties properties = new Properties();
+
+ try {
+properties.load(new
+ this.publisherName = publisherName;
+ messageApi = marconiApi.getMessageApiForZoneAndClientAndQueue(ZONE,
PUBLISHER_ID, NAME);
+ }
+
+ public void run() {
+ for (int i = 0; i 32; i++) {
+messageApi.create(publish(i));
+
+System.out.format( Subscriber %s Message %s:%s (%s)%n,
subscriberName,
+ props.getProperty(PUBLISHER_NAME),
props.getProperty(MESSAGE_NUM), props.getProperty(MESSAGE_TEXT));
+ }
+ }
+
+ private Properties loadStringProperties(String body)
+ private void createQueue() {
+ queueApi.create(NAME);
+ }
+
+ private void createMessages() throws ExecutionException,
InterruptedException {
+ System.out.format(Create Messages%n);
+
+ MessageApi messageApi =
+ streamMessages.deleteQueue();
+ } catch (Exception e) {
+ e.printStackTrace();
+ } finally {
+ streamMessages.close();
+ }
+ }
+
+ public StreamMessages(String username, String apiKey) {
+ // If this application we're running *inside* the
@@ -320,6 +321,56 @@ Note: This uses the API key, not the password.
In addition to the CreatePolicy example, by going through the Auto Scale
example code, you will learn to create and execute webhooks, and delete and
modify groups, policies, and webhooks. You can find the examples
+
+Producer Consumer
+ Producer 1 Message 1:0
+ Producer 1 Message 1:1
+ Consumer 1 Message 1:0 (Queue This Way)
+ Consumer 2 Message 1:1 (Queue This Way)
+ Producer 1 Message 1:2
+ Consumer 1 Message 1:2 (Queue This Way)
+ Producer 1 Message 1:3
+
Couple of minor comments, but otherwise +1 - looks good. Links seem to work,
too, although the links to the code samples themselves are still 404s as that
PR is still waiting to be merged, I guess.
---
Reply to this email directly or view it on GitHub:
@abayer @andrewgaul Look OK for a squash'n'rebase?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/44#issuecomment-31202964
PS: Javadoc link live now, too:
http://demobox.github.io/jclouds-maven-site-1.7.0/1.7.0/jclouds/apidocs/
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/44#issuecomment-31206677
I expect to write something this week. It would be good to start a
blog section in jclouds.apache.org, but if we do that we should keep
writing posts (a dead page/blog gives a bad impression of the project
health).
What does people think about starting such a section?
Rather than starting
I don't know if we have the credentials. Anyway, I think that we should
migrate from thumblr to Jekyll, to have everything in the jclouds-site
repo. Adding blog posts then would be super easy. WDYT?
Writing the post itself would be easy, but I don't know what kind of
support in terms of RSS
Following on from Ignasi's suggestion, here a first attempt to
describe jclouds' core concepts. May still be a little too
developer-centric (hence the initial location on the dev wiki), but I
hope it's at least a useful start...
https://wiki.apache.org/jclouds/Core%20Concepts
ap
Ok, then I'll start a blog branch and migrate all posts in thumblr to
jclouds-site and see how it looks like!
Thanks! Interesting PR coming up ;-)
ap
Thanks, @nirmal070125! Could you raise this against the current jclouds repo?
https://github.com/jclouds/jclouds
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/legacy-jclouds.github.com/pull/151#issuecomment-31356953
@@ -29,6 +29,8 @@ The wire log is used to log all data transmitted to and
from servers when execut
Because the content of HTTP requests is usually less important for debugging
than the HTTP headers, these two types of data have been separated into
different wire logs.
+NOTE: Wire
Just wondering $subject. We are pretty reluctant to move to the latest
version of jclouds at this moment of time, hence the question.
Yes, certainly! Please submit then against the relevant branch, e.g.
the 1.6.x branch [1] for the 1.6.2-incubating release.
We may also want to port these
nearby events.
+
+* **8 Feb:** jcloudsTraining@Citerus - First comprehensive jclouds training,
a 3-day dive into ComputeService led by Mattias Holmqvist and I.
+* **15 Feb:** MultiPaaS@Jfokus - Multi-PaaS session by Andrew Phillips,
including decision making in PaaS and experiences taking our
@@ -0,0 +1,14 @@
+---
+layout: post
+title: jclouds 1.6.0 released!
+author: Adrian Cole
+tumblr_url: http://jclouds.tumblr.com/post/49146565342/jclouds-1-6-0-released
+---
+
+jclouds 1.6 represents 7 months of refactoring to essentially reset the
project 4 years after its founding. The
+author: Adrian Cole
+tags: jclouds cloud openstack rackspace ec2 buildhive cloudbees java
+tumblr_url:
http://jclouds.tumblr.com/post/35922275965/jclouds-1-5-3-out-the-door
+---
+
+Released on 2012-11-14, jclouds 1.5.3 includes minor fixes, and a few
important updates.
+
+* New
@@ -0,0 +1,37 @@
+---
+layout: post
+title: Catching exceptions with less keystrokes
I guess that should be fewer keystrokes, but it's in the original post, so...
;-)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/47/files#r8608929
A couple of minor comments, but otherwise looks great. Thanks, @nacx!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/47#issuecomment-31440989
Looks ready for a squash, rebase'n'merge to me! +1.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/47#issuecomment-31450318
@@ -0,0 +1,58 @@
+---
+layout: jclouds
+title: Quick Start - SoftLayer CloudLayer Compute
+---
+
+# Quick Start: SoftLayer CloudLayer Compute
+
+This page helps you get started with jclouds API with SoftLayer CloudLayer
Compute and to create Cloud Compute Instances
+
+1. Sign up for
@@ -0,0 +1,58 @@
+---
+layout: jclouds
+title: Quick Start - SoftLayer CloudLayer Compute
+---
+
+# Quick Start: SoftLayer CloudLayer Compute
+
+This page helps you get started with jclouds API with SoftLayer CloudLayer
Compute and to create Cloud Compute Instances
+
+1. Sign up for
+
+// List availability zones
+Set? extends Location locations = compute.listAssignableLocations();
+
+// List nodes
+Set? extends ComputeMetadata nodes = compute.listNodes();
+
+// List hardware profiles
+Set? extends Hardware hardware = compute.listHardwareProfiles();
+
+// List
+Set? extends org.jclouds.compute.domain.Image image =
compute.listImages();
+
+// Create nodes with templates
+Template template =
compute.templateBuilder().osFamily(OsFamily.UBUNTU).build();
+// by default, all the nodes created by jclouds will have `jclouds.org` as
domain name.
+// by default, all the nodes created by jclouds will have `jclouds.org` as
domain name.
+// If you want to edit that default value, you can specify something like:
+// Template template =
compute.templateBuilder().options(SoftLayerTemplateOptions.Builder.domainName(yourDomainName))
+//
Thanks @demobox I've just submitted a new commit
Yes, saw that as soon as I refreshed after leaving my comment ;-) Thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/49#issuecomment-31468097
The new blog is live!
Cl! And now you can see straight away that we haven't published
anything since 2013 ;-)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/47#issuecomment-31470045
demobox, any chance you could reach out to the CloudBees guys and see if
they can figure out why we keep having build failures like this one and the
others with Maven repo issues?
I've opened a ticket. The flood of emails is getting a
trifle...erm...annoying, indeed.
Do we want to force users to sign in to comment, or do we want to enable [guest
comments](http://help.disqus.com/customer/portal/articles/832187-guest-commenting)?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/50#issuecomment-31489174
@shrinandj: thanks for the update. Have you been able to discuss this PR with
@andrewgaul?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/214#issuecomment-31489268
+import static
org.jclouds.examples.rackspace.cloudqueues.Constants.NUM_THREADS;
+import static
org.jclouds.examples.rackspace.cloudqueues.Constants.PRODUCER_ID;
+import static
org.jclouds.examples.rackspace.cloudqueues.Constants.PRODUCER_NAME;
+import static
@@ -112,7 +125,8 @@ public boolean equals(Object obj) {
Objects.equal(this.type, that.type)
Objects.equal(this.cooldown, that.cooldown)
Objects.equal(this.target, that.target)
-Objects.equal(this.targetType, that.targetType);
+
@@ -84,6 +84,7 @@
((Double)scalingPolicyMap.get(cooldown)).intValue(),
DoubleMath.isMathematicalInteger(d) ?
Integer.toString(d.intValue()) : Double.toString(d),
targetType,
+ (MapString,
@@ -81,6 +81,7 @@ public ScalingPolicyResponse apply(HttpResponse from) {
((Double)scalingPolicyMap.get(cooldown)).intValue(),
DoubleMath.isMathematicalInteger(d) ?
Integer.toString(d.intValue()) : Double.toString(d),
targetType,
@@ -96,6 +96,11 @@
} else {
scalingPolicyMapBuilder.put(scalingPolicy.getTargetType().toString(),
targetString);
}
+
+ if(scalingPolicy.getSchedulingArgs() != null
Space after `if`?
---
Reply to this email directly or view it on GitHub:
@@ -0,0 +1,11 @@
+[
+ {
+args: {
+cron: 23 * * * *
+},
+changePercent: -5.5,
+cooldown: 2,
+name: scale down by 5.5 percent at 11pm,
+type: schedule
+ }
[minor] indenting here?
---
Reply to this email directly or view it on
+1 - looks good to me. Just waiting on BuildHive etc.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/242#issuecomment-31532239
@@ -198,6 +198,10 @@ public String getResult() {
@PUT
@Path(/objects/{id})
void putNothing(@PathParam(id) String id);
+
+ @POST
+ @Path(/objects/{id})
+ void postNothing(@PathParam(id) String id);
enviarNada, no?;-)
---
Reply to this email directly or view it on
@@ -0,0 +1,16 @@
+jclouds OkHttp driver
+=
+
+A driver to use the OkHttp (http://square.github.io/okhttp/) client as an
HTTP library in jclouds.
+
+This driver allows using modern HTTP verbs such as PATCH in the providers
and APIs, and also
+provider SPDY support.
+dependency
+ groupIdcom.squareup.okhttp/groupId
+ artifactIdokhttp/artifactId
+ version${okhttp.version}/version
+/dependency
+dependency
+ groupIdcom.squareup.okhttp/groupId
+ artifactIdmockwebserver/artifactId
+ version${okhttp.version}/version
@@ -252,6 +252,11 @@
version8.1.8.v20121106/version
/dependency
dependency
+groupIdcom.squareup.okhttp/groupId
+artifactIdmockwebserver/artifactId
+version1.2.1/version
Already introduced in the driver POM, I see...perhaps simply move into the
-* Ensures the content is always flushed.
-*
-*/
- static class ConsumeOnCloseInputStream extends FilterInputStream {
-
- protected ConsumeOnCloseInputStream(InputStream in) {
- super(in);
- }
-
- boolean closed;
-
- @Override
- public
I've opened a ticket. The flood of emails is getting a
trifle...erm...annoying, indeed.
https://cloudbees.zendesk.com/requests/15302
CloudBees have restarted their internal Maven repo. I'll keep
monitoring the builds and will reopen the ticket if that doesn't help...
Another bunch of build
-* Ensures the content is always flushed.
-*
-*/
- static class ConsumeOnCloseInputStream extends FilterInputStream {
-
- protected ConsumeOnCloseInputStream(InputStream in) {
- super(in);
- }
-
- boolean closed;
-
- @Override
- public
I can't figure out why the current behavior is useful, so this patch removes
ConsumeOnCloseInputStream and uses
a standard input stream.
@adriancole @andrewgaul Any wisdom you could share as to the background for
this code, and why it may (not) be wise to remove it? Thanks!
---
Reply to
@@ -38,8 +32,6 @@
* This example will create a container, put a file in it, and publish it on
the internet!
*/
public class CloudFilesPublish implements Closeable {
- private final BlobStore blobStore;
- private final RestContextCommonSwiftClient, CommonSwiftAsyncClient
swift;
Not sure why the pull request builders didn't kick off - let me try a
close'n'reopen to see if that helps. Looks good to me, though - +1
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/28#issuecomment-31641395
Looks good to me, but interested to see if @everett-toews has some more
comments. Squash'n'rebase too, obviously
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/71#issuecomment-31689929
Perhaps a single line underneath that says, There are also
views/abstractions/whatever for Loadbalancers (link)
and the next one and the next one.
Agree. BlobStore and Compute are certainly the most important ones so far, and
the symmetry is nice visually, too.
I quite like the use of
Nice!! Perhaps make one in `Apache jclouds® is a cloud agnostic library...`
italic, bold or underlined?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31750810
+ public String getSchedulingString() {
+ if (this.args != null) {
+ for (Map.EntryString, String entry : this.args.entrySet()) {
+return entry.getValue();
+ }
+ }
+ return null;
+ }
+
+ /**
+* @return The type of the schedule this
Because this is a backport, I am not sure this should be squashed, but I also
did not think there is any need to
split it into 2 different PRs. Thoughts?
Ah, so this is two straight commits cherry-picked? Then let's obviously keep
as-is and address any comments separately.
+1 - thanks for
What's the width of your screen?
It's 1366px, but the browser window was indeed not full screen. If I fullscreen
it, it's no longer balanced? And the provider logos still look a bit cramped
(Chrome 31.0.1650.63 on Windows 7):
+/**
+ * Thrown when an object cannot be copied.
+ *
+ * @author Everett Toews
+ */
+public class CopyObjectException extends ResourceNotFoundException {
+
+ private String sourcePath;
+ private String destinationPath;
+
+ public CopyObjectException() {
+ super();
+ }
+
+ private String destinationPath;
+
+ public CopyObjectException() {
+ super();
+ }
+
+ public CopyObjectException(String sourcePath, String destinationPath,
String message) {
+ super(String.format(Either the source path %s or the destination path
%s was not found. +
*
* @see a
*
href=http://docs.openstack.org/api/openstack-object-storage/1.0/content/Update_Container_Metadata-d1e1900.html;
* Create or Update Object Metadata API/a
*
-* @return codetrue/code if the Object Metadata was successfully
created
+
@@ -184,7 +189,7 @@ boolean deleteMetadata(@PathParam(objectName) String
objectName,
@BinderParam(BindRemoveObjectMetadataToHeaders.class) MapString,
String metadata);
/**
-* Deletes a object, if present.
+* Delete an object, if present.
Use 3rd person rather
@@ -197,4 +202,32 @@ boolean deleteMetadata(@PathParam(objectName) String
objectName,
@Fallback(VoidOnNotFoundOr404.class)
@Path(/{objectName})
void delete(@PathParam(objectName) String objectName);
+
+ /**
+* Copy an object from one container to another. Please note
@@ -162,15 +168,14 @@ boolean updateMetadata(@PathParam(objectName) String
objectName,
@BinderParam(BindObjectMetadataToHeaders.class) MapString, String
metadata);
/**
-* Deletes Object metadata.
+* Delete the metadata from a {@link SwiftObject}.
Deletes (see
@@ -140,18 +146,18 @@ String replace(@PathParam(objectName) String
objectName, @BinderParam(SetPaylo
SwiftObject get(@PathParam(objectName) String objectName, GetOptions
options);
/**
-* Creates or updates the Object metadata.
+* Create or update the metadata for a
@@ -49,10 +51,21 @@ public void handleError(HttpCommand command, HttpResponse
response) {
exception = new AuthorizationException(exception.getMessage(),
exception);
break;
case 404:
-if
@@ -49,10 +51,21 @@ public void handleError(HttpCommand command, HttpResponse
response) {
exception = new AuthorizationException(exception.getMessage(),
exception);
break;
case 404:
-if
@@ -16,3 +16,4 @@ rackspace/bin/
lein
project.clj
.lein-deps-sum
+*.DS_STORE
Do we need `*.DS_STORE` here or would `.DS_STORE` be enough?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/29/files#r8709950
@@ -49,10 +51,21 @@ public void handleError(HttpCommand command, HttpResponse
response) {
exception = new AuthorizationException(exception.getMessage(),
exception);
break;
case 404:
-if
401 - 500 of 1315 matches
Mail list logo
