+ *
+/jclouds.osgi.import
+ /properties
+
+ repositories
+repository
+ idapache-snapshots/id
+ urlhttps://repository.apache.org/content/repositories/snapshots/url
+ releases
+enabledfalse/enabled
+ /releases
+ snapshots
+
+ scopetest/scope
+/dependency
+dependency
+ groupIdch.qos.logback/groupId
+ artifactIdlogback-classic/artifactId
+ scopetest/scope
+/dependency
+dependency
+ groupIdorg.apache.jclouds.api/groupId
+ artifactIdrackspace-cloudidentity/artifactId
@demobox +1. Thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/281#issuecomment-34621511
[
https://issues.apache.org/jira/browse/JCLOUDS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13896630#comment-13896630
]
Jeremiah Robertson commented on JCLOUDS-443:
Sorry, I have another question.
[
https://issues.apache.org/jira/browse/JCLOUDS-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Phillips updated JCLOUDS-432:
Affects Version/s: 1.6.4
Revert Guava/7u51 incompatibility workaround as soon as Guava
Committed to master:
[#1](https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=02615adc4f45799d07f61727167b65c87458f573),
[#2](https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=4c07702d29de64df45c11819c2cc9d725382b0c2).
---
Reply to this email directly or view it on
[
https://issues.apache.org/jira/browse/JCLOUDS-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Phillips updated JCLOUDS-432:
Attachment: JCLOUDS-432.patch
Revert Guava/7u51 incompatibility workaround as soon as
Another verification build running against master [using
7u51](https://jclouds.ci.cloudbees.com/job/jclouds-java-7u51/36/console)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/281#issuecomment-34643210
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds$jclouds-compute/2536/
I asked about a 15.0.1 release in the upstream Guava issue:
https://code.google.com/p/guava-libraries/issues/detail?id=1635#c45
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/281#issuecomment-34651577
[
https://issues.apache.org/jira/browse/JCLOUDS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13896743#comment-13896743
]
Jeremiah Robertson commented on JCLOUDS-443:
Awesome, sounds good. Thank you
I asked about a 15.0.1 release in the upstream Guava issue:
I saw that, thanks @andrewgaul! Curious to see if there'll be any response...
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/281#issuecomment-34652502
Andrew Gaul created JCLOUDS-459:
---
Summary: Limit number of user threads
Key: JCLOUDS-459
URL: https://issues.apache.org/jira/browse/JCLOUDS-459
Project: jclouds
Issue Type: Improvement
Sorry for ignoring this. By default jclouds uses an unlimited number of user
threads, set in ```BaseApiMetadata.defaultProperties```. I believe this will
cause problems for users of Atmos blobstores. We can work around this by
setting a lower number in
See https://jclouds.ci.cloudbees.com/job/jclouds-karaf/561/
+ *
+/jclouds.osgi.import
+ /properties
+
+ repositories
+repository
+ idapache-snapshots/id
+ urlhttps://repository.apache.org/content/repositories/snapshots/url
+ releases
+enabledfalse/enabled
+ /releases
+ snapshots
+
+ *
+/jclouds.osgi.import
+ /properties
+
+ repositories
+repository
+ idapache-snapshots/id
+ urlhttps://repository.apache.org/content/repositories/snapshots/url
+ releases
+enabledfalse/enabled
+ /releases
+ snapshots
+
You can merge this Pull Request by running:
git pull https://github.com/maginatics/jclouds atmos-500-1040
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds/pull/285
-- Commit Summary --
* JCLOUDS-137: Retry on HTTP 500 AtmosError 1040
-- File
@shrinandj relevant to your interests.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/285#issuecomment-34682671
The turnaround time on this is INCREDIBLE!! :+1:
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/285#issuecomment-34685027
@shrinandj relevant to your interests.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/286#issuecomment-34686120
Previously jclouds could use an unlimited number of threads on its
user ExecutorService. While this ExecutorService will go away when we
complete deasyncafication, we should prevent jclouds from misbehaving
until that time.
You can merge this Pull Request by running:
git pull
[jclouds » jclouds
#827](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/827/) 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:
[jclouds-java-7-pull-requests
#1056](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1056/)
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/285#issuecomment-34687928
[jclouds-pull-requests
#584](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/584/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/285#issuecomment-34687898
Spurious test failure, tracked by
[JCLOUDS-429](https://issues.apache.org/jira/browse/JCLOUDS-429).
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/285#issuecomment-34688336
[jclouds-java-7-pull-requests
#1058](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1058/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/287#issuecomment-34694397
+ .clusterType(in.getClusterType())
+ .flavorId(in.getFlavorId())
+ .nodeCount(in.getNodeCount())
+ .postInitScript(in.getPostInitScript());
+ }
+ }
+
+ @Override
+ public int compareTo(CreateCluster that) {
+
[jclouds-labs-openstack-pull-requests
#160](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/160/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/78#issuecomment-34715615
Andrew Gaul created JCLOUDS-461:
---
Summary: aws-s3 live tests have many bucket does not exist failures
Key: JCLOUDS-461
URL: https://issues.apache.org/jira/browse/JCLOUDS-461
Project: jclouds
[
https://issues.apache.org/jira/browse/JCLOUDS-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated JCLOUDS-461:
Description:
I see many bucket does not exist failures when running:
$ mvn integration-test -pl
Andrew Gaul created JCLOUDS-462:
---
Summary: many aws-ec2 live tests fail
Key: JCLOUDS-462
URL: https://issues.apache.org/jira/browse/JCLOUDS-462
Project: jclouds
Issue Type: Bug
+ private int retryCountLimit = 5;
+ @Resource
+ protected Logger logger = Logger.NULL;
+
+ public boolean shouldRetryRequest(HttpCommand command, HttpResponse
response) {
+ if (command.getFailureCount() retryCountLimit) {
+ return false;
+ }
+ if
33 matches
Mail list logo
