aws labs is now at https://github.com/jclouds/jclouds-labs-aws

[codefromthecrypt]

With jclouds 1.6.0 final out, we can now move development of aws into its new home at https://github.com/jclouds/jclouds-aws-google

This will be a temporary place until it is merged into an apache repository per issue #1576

Note I've setup buildhive pull request hooks and will setup snapshot publishing as soon as this is merged.

commands I used to create the new repo off master:

git clone https://github.com/jclouds/jclouds-labs.git
git filter-branch --prune-empty --subdirectory-filter aws master
git push -f https://github.com/jclouds/jclouds-labs-aws.git master

I followed that up with a cleanup of pom.xml and added default README.md and .gitignore

[buildhive]

Adrian Cole » jclouds-labs #105 SUCCESS This pull request looks good (what's this?)

[codefromthecrypt]

added snapshot build: https://jclouds.ci.cloudbees.com/view/labs/job/jclouds-aws-openstack/ https://github.com/jclouds/jclouds-labs-aws/settings/hooks

[codefromthecrypt]

first build failed due to some jenkinsy thing. second went fine without any changes to the repo or config. https://jclouds.ci.cloudbees.com/view/labs/job/jclouds-labs-aws/2/console

[demobox]

@adriancole Should this be a public job? I'm guessing yes..?

[codefromthecrypt]

yes. I missed a switch. you mind sorting that?

On Mon, Apr 29, 2013 at 6:31 AM, Andrew Phillips notifications@github.comwrote:

@adriancole https://github.com/adriancole Should thishttps://jclouds.ci.cloudbees.com/view/labs/job/jclouds-labs-aws/be a public job? I'm guessing yes..?

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds-labs/pull/92#issuecomment-17166553 .

[demobox]

Settings were already correct (or thanks to whoever did that) - just also added them to https://jclouds.ci.cloudbees.com/view/public/