[jclouds-karaf-pull-requests
#71](https://jclouds.ci.cloudbees.com/job/jclouds-karaf-pull-requests/71/)
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/43#issuecomment-40684294
[jclouds » jclouds-karaf
#909](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-karaf/909/)
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-karaf-pull-requests #71 UNSTABLE
Whee! No [test
failures](https://jclouds.ci.cloudbees.com/job/jclouds-karaf-pull-requests/org.apache.jclouds.karaf$itests/71/testReport/)!
Just Checkstyle complaining now.
---
Reply to this email directly or view it on GitHub:
@nacx: Do you have any idea how to _test_ the agentproxy stuff via Karaf?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/43#issuecomment-40705813
@demobox: It is both ok and required to also list the transitive dependencies.
The goal of the feature xml is to list all runtime dependencies of that
particular feature. The flag dependency = true is a good idea to be used when
listing dependencies of that particular feature (but not the core
Thanks, @iocanel! My question perhaps wasn't clear. I understand that we need
to list transitive deps _in the feature.xml_ - I was wondering whether we also
need to list them _in the POM_. E.g. the three jsch-agentproxy deps we list in
`feature.xml` are all brought in by **one** dep in the POM.
@everett-toews @andrewgaul Would you be OK with merging this PR as-is to get
the release rounded off, and then potentially deciding on changing the
versioning scheme in a different PR?
---
Reply to this email directly or view it on GitHub:
The jclouds Maven group ID for versions since 1.6.1-incubating is
`org.apache.jclouds` rather than `org.jclouds` or something like that, to get
the group ID bit to the beginning of the sentence?
---
Reply to this email directly or view it on GitHub:
This link requires a login? Change or remove?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/commit/d268420e6de87f45a78db4c996c509224d3057a6#commitcomment-6042861
Apache jclouds PMC and community for verifying the release?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/commit/d268420e6de87f45a78db4c996c509224d3057a6#commitcomment-6042866
@everett-toews: Thanks for the updates. Dang...added comments to the
[commit](https://github.com/jclouds/jclouds-site/commit/d268420e6de87f45a78db4c996c509224d3057a6)?utm_campaign=websiteutm_source=sendgrid.comutm_medium=email
rather than in the PR.
---
Reply to this email directly or view it
@everett-toews: Thanks for the updates. Dang...added comments to the
[commit](https://github.com/jclouds/jclouds-site/commit/d268420e6de87f45a78db4c996c509224d3057a6)
rather than in the PR.
---
Reply to this email directly or view it on GitHub:
[jclouds-site-pull-requests
#254](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/254/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/79#issuecomment-40713303
@@ -114,14 +114,21 @@ You'll also need a logback.xml configuration file on
your classpath. Here's an e
## a id=enable/aEnable Logging
-Below is some example code of how to enable your code to use SLF4J. The
SLF4JLoggingModule needs to be passed in to the ContextBuilder of whatever
[jclouds-site-pull-requests
#255](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/255/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40715604
Go to
http://ec47fb9b84b47dd75b2f-c49bf12d82edef417c3e504e70fd4a52.r58.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40715779
+1 - thanks, @everett-toews!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/79#issuecomment-40717919
How about linking to
http://people.apache.org/committers-by-project.html#jclouds and/or
http://people.apache.org/committers-by-project.html#jclouds-pmc? There's some
noise on the former, admittedly...
---
Reply to this email directly or view it on GitHub:
Whatever works for you. I’ll be offline for the next hour or so. Go ahead and
update and deploy. :)
On Apr 17, 2014, at 9:15 AM, Andrew Phillips
notificati...@github.commailto:notificati...@github.com wrote:
How about linking to
http://people.apache.org/committers-by-project.html#jclouds
I'm a +1 here. Ready to go when you are
Thanks, @everett-toews! Just squashed and rebased - final check and then we're
good to go, I think. Javadocs are also almost done.
---
Reply to this email directly or view it on GitHub:
[jclouds-site-pull-requests
#256](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/256/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40720752
Go to
http://453f11b7ed217050435f-440cff09bce96ffb010c210def461267.r51.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40721002
Spotted a type (old group ID) - one more round.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40722147
[jclouds-site-pull-requests
#257](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/257/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40722545
Go to
http://3573bb7f449158a49916-f485765c0d4b95cf8ed4cf6bf7fe1442.r26.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40722718
Committed to
[master](https://git-wip-us.apache.org/repos/asf?p=jclouds-examples.git;a=commit;h=300d46022632ddcb4c6682f523760e53319314d1)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/43#issuecomment-40722874
Closed #43.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/43
jclouds » jclouds-labs #974 UNSTABLE
jclouds-labs-pull-requests #138 UNSTABLE
Thanks for the update, @andreaturli! We now have [one test
Thanks @demobox I will.
Not sure about the latest 2 checkstyle violations: any hint?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/57#issuecomment-40726804
@demobox Do you need me to deploy this? I'm excited to get the release out
there!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40727917
[jclouds » jclouds-labs
#975](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/975/) 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-labs-pull-requests
#139](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/139/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/57#issuecomment-40729306
@pimenas Sounds like a plan, no objections! The `getConsole()` method
definitely leaves the options open for new types of consoles in the future.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/339#issuecomment-40733191
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-site twitter
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/81
-- Commit Summary --
* Added a Twitter timeline to the community page
-- File
[jclouds-site-pull-requests
#258](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/258/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/81#issuecomment-40734365
[jclouds-site-pull-requests
#259](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/259/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/81#issuecomment-40734594
Go to
http://e8333fd32b0549c399cb-c2224fb70f4efe9b8aebf1de8a086b1b.r63.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/81#issuecomment-40734756
Mikołaj Zalewski created JCLOUDS-535:
Summary: Create examples of using GCE with jclouds
Key: JCLOUDS-535
URL: https://issues.apache.org/jira/browse/JCLOUDS-535
Project: jclouds
Issue
[
https://issues.apache.org/jira/browse/JCLOUDS-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13973132#comment-13973132
]
Mikołaj Zalewski commented on JCLOUDS-535:
--
First example Pull Request:
Do you need me to deploy this? I'm excited to get the release out there!
About to do that. Just got out of a meeting ;-)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40742639
This PR updates the Rackspace Examples to use the new OpenStack Swift API.
JIRA: https://issues.apache.org/jira/browse/JCLOUDS-346
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-examples cloudfiles-updates
Or you can view, comment on it, or merge it
I don't see any reason why we should have those dependencies in the pom.xml
You mean the transitive ones, I guess? The main one needs to be in there so
we can use `bundle dependency=true`, no? Or should we even skip that and
simply use `bundle`?
Sorry, noob questions here! ;-)
---
Reply to
This simple PR updates the various OpenStack and Rackspace service types to the
latest known services.
The jclouds-labs-openstack project will need to be updated to the new types
once this PR is merged.
cc @everett-toews @zack-shoylev
You can merge this Pull Request by running:
git pull
[
https://issues.apache.org/jira/browse/JCLOUDS-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13973255#comment-13973255
]
Jeremy Daggett commented on JCLOUDS-346:
Examples update in the following PR:
Published (rev 1588338). A _lot_ of stuff was pushed there - everything looks
OK, but if you could take a quick look, @everett-toews, that'd be appreciated.
Thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40748219
@demobox @everett-toews @zack-shoylev The `QuotaClassApi` looks to have been
removed and integrated into the `os-quota-sets` API:
http://api.openstack.org/api-ref-compute-v2-ext.html#ext-os-quota-sets
My feeling right now is that we can remove this API, with the understanding
that we add
You can merge this Pull Request by running:
git pull https://github.com/jclouds/jclouds-site update-readme
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/82
-- Commit Summary --
* Updating publishing instructions in the README
--
[jclouds-site-pull-requests
#260](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/260/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/82#issuecomment-40750795
Go to
http://2a8818dc75d5c3397ad6-9285a353174ed2b546b53448d00e322a.r26.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/82#issuecomment-40750992
Jeremy Daggett created JCLOUDS-536:
--
Summary: Support Nova Quota Sets Extension API
Key: JCLOUDS-536
URL: https://issues.apache.org/jira/browse/JCLOUDS-536
Project: jclouds
Issue Type:
[jclouds-pull-requests
#762](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/762/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/350#issuecomment-40752928
LGTM. Thanks @demobox!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40753025
+1
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/82#issuecomment-40753088
Closed #82.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/82
Thanks, @everett-toews. Committed to
[master](https://git-wip-us.apache.org/repos/asf?p=jclouds-site.git;a=commit;h=2d0e5f9f016952e9382c486f498b94294bc00e12)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/82#issuecomment-40754229
Not sure about the latest 2 checkstyle violations: any hint?
Ah, yes...that one. The warning is not very helpful, I'm afraid :-( I think
it's missing newline at end of file.
The place to verify that, by the way, is in the [Checkstyle result file in the
PS: Thanks for the cleanup, of course, @andreaturli!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/57#issuecomment-40754567
@jdaggett @demobox : The os-quota-sets API actually already exists in JClouds
separately:
[QuotaAsyncApi.java](https://github.com/jclouds/jclouds/blob/master/apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/extensions/QuotaAsyncApi.java)
---
Reply to this email directly or view
Can you please run through all of the ctors and update the URLs?
Should be http://jclouds.apache.org/guides/rackspace/
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/45#issuecomment-40758113
[jclouds-labs-pull-requests
#140](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/140/)
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/57#issuecomment-40757727
jclouds-labs-pull-requests #140 FAILURE
Some internal DEV@cloud failure.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/57#issuecomment-40758454
[jclouds » jclouds-labs
#977](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/977/) 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:
This should be merged now.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/32#issuecomment-40759453
About to merge
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/32#issuecomment-40759475
It seems this needs a rebase first...
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/32#issuecomment-40759739
Well... oops.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/commit/af9cd528f52bf147ac8c2ace33be6bda8d5c7487#commitcomment-6049238
Good to have GCE examples, thanks @mikolajz!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/44?utm_campaign=websiteutm_source=sendgrid.comutm_medium=email#issuecomment-40762260
Looks good to me too!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/348#issuecomment-40762944
merged
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/32#issuecomment-40763278
@@ -0,0 +1,31 @@
+package org.jclouds.examples.google.computeengine;
Good catch...thanks, @nacx!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/44/files#r11754332
Apart from what @andrewgaul said, we should have a unit test for this.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/338#issuecomment-40763386
Well... oops.
Sorry, missing something here ;-) Do we want this change or not?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/commit/af9cd528f52bf147ac8c2ace33be6bda8d5c7487#commitcomment-6049378
Code changes themselves look good to me. I'll let @zack-shoylev or
@everett-toews comment on the validity of the new entries in `ServiceType.java`
Thanks, @jdaggett!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/350#issuecomment-40764032
After the main method comments are fixed I'm a +1. I ran all of the examples
and everything is fine.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/45#issuecomment-40765742
Merged and deployed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/81#issuecomment-40765842
Jeremy Daggett created JCLOUDS-537:
--
Summary: Update blobstore examples
Key: JCLOUDS-537
URL: https://issues.apache.org/jira/browse/JCLOUDS-537
Project: jclouds
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/JCLOUDS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett reassigned JCLOUDS-537:
--
Assignee: Jeremy Daggett
Update blobstore examples
-
[
https://issues.apache.org/jira/browse/JCLOUDS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett updated JCLOUDS-537:
---
Labels: blobstore examples (was: )
Update blobstore examples
-
[
https://issues.apache.org/jira/browse/JCLOUDS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett updated JCLOUDS-537:
---
Component/s: jclouds-examples
jclouds-blobstore
Update blobstore examples
[
https://issues.apache.org/jira/browse/JCLOUDS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett updated JCLOUDS-537:
---
Affects Version/s: 1.7.3
Update blobstore examples
-
[
https://issues.apache.org/jira/browse/JCLOUDS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13973481#comment-13973481
]
Jeremy Daggett commented on JCLOUDS-537:
This issue is to track updated to
@demobox Spoke too soon. In your commit, the contents of the
/releasenotes/atom.xml entries was markdown instead of the generated html that
it should have been. See this
[diff](http://svn.apache.org/viewvc/jclouds/site-content/releasenotes/atom.xml?view=diffr1=1588337r2=1588338pathrev=1588338).
@demobox My opinion is that the extension should be *removed*, but lets get
input from @everett-toews and @zack-shoylev before deciding to remove it.
@jasdeep-hundal Oh, thanks, you are right! That wasn't apparent to me based on
the API name!
From the latest docs, the following fields appear
[
https://issues.apache.org/jira/browse/JCLOUDS-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett updated JCLOUDS-536:
---
Description:
JCLOUDS-526 proposes the removal of the legacy Nova QuotaClassApi, however the
we should have a unit test for this
Good catch, @shrinandj - yes, indeed, we're missing a test here.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/338#issuecomment-40775344
@shrinandj @demobox Yes, there is no test there now, but there will be.I will
get back to this PR next week.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/338#issuecomment-40775757
I assume you were using jekyll 1.5.1
Yes, 1.5.1 Checking rdiscount now...
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40775919
@@ -45,7 +47,14 @@ public SwiftObject apply(Blob from) {
return null;
SwiftObject object =
objectProvider.create(blob2ObjectMd.apply(from.getMetadata()));
object.setPayload(checkNotNull(from.getPayload(), payload: + from));
-
gem list | grep rdiscount
```
rdiscount (2.1.7.1)
```
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/78#issuecomment-40776321
@everett-toews: How about just patching it with
http://3573bb7f449158a49916-f485765c0d4b95cf8ed4cf6bf7fe1442.r26.cf1.rackcdn.com/releasenotes/atom.xml
for now while we figure out what might have happened?
---
Reply to this email directly or view it on GitHub:
Are you sure it's broken?
[HEAD](http://svn.apache.org/viewvc/jclouds/site-content/releasenotes/atom.xml?view=markup)
and [the actual file](http://jclouds.apache.org/releasenotes/atom.xml) both
look OK. Can't make sense of the diff, I have to admit.
---
Reply to this email directly or view it
@@ -177,6 +177,26 @@ private String getMessage(final String containerName,
return listing;
}
+ private ListenableFutureVoid deleteDirectory(
[minor] Could you move `final ListContainerOptions options, ` up one row?
---
Reply to this email directly or view it on GitHub:
Just to make sure I'm understanding this correctly: it's purely a refactoring
commit? Only one minor formatting comment, otherwise looks good to me.
Thanks, @shrinandj!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/349#issuecomment-40781268
93 matches
Mail list logo
