Re: [jclouds] Support for OpenStack OS-Services API (#573)

[CloudBees pull request builder plugin]

[jclouds-pull-requests 
#1288](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1288/) SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/573#issuecomment-58852067

Re: [jclouds] Support for OpenStack OS-Services API (#573)

[CloudBees pull request builder plugin]

[jclouds-pull-requests-java-6 
#199](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests-java-6/199/) 
SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/573#issuecomment-58850088

[jclouds] Support for OpenStack OS-Services API (#573)

[Avi Ben-Harush]

You can merge this Pull Request by running:

  git pull https://github.com/avibh/jclouds-1 apache-master

Or you can view, comment on it, or merge it online at:

  https://github.com/jclouds/jclouds/pull/573

-- Commit Summary --

  * Support for OpenStack OS-Services API

-- File Changes --

M 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/NovaApi.java 
(10)
M 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/config/NovaHttpApiModule.java
 (2)
A 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/domain/OsService.java
 (235)
M 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/extensions/ExtensionNamespaces.java
 (5)
A 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/extensions/OsServicesApi.java
 (93)
A 
apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/extensions/OsServicesApiExpectTest.java
 (75)
A 
apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/extensions/OsServicesApiLiveTest.java
 (87)
M apis/openstack-nova/src/test/resources/extension_list_full.json (8)
A apis/openstack-nova/src/test/resources/os_services_list.json (36)

-- Patch Links --

https://github.com/jclouds/jclouds/pull/573.patch
https://github.com/jclouds/jclouds/pull/573.diff

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/573

Re: [jclouds] Support for OpenStack Services API (#572)

[CloudBees pull request builder plugin]

[jclouds-pull-requests-java-6 
#198](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests-java-6/198/) 
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/pull/572#issuecomment-58846254

Re: [jclouds] Support for OpenStack Services API (#572)

[CloudBees pull request builder plugin]

[jclouds-pull-requests 
#1287](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1287/) 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/pull/572#issuecomment-58846247

Re: [jclouds] Support for OpenStack Services API (#572)

[BuildHive]

[jclouds » jclouds 
#1790](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1790/) FAILURE
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/jclouds/pull/572#issuecomment-58846227

Build failed in Jenkins: jclouds » jclouds #1790

[BuildHive]

See 

--
GitHub pull request #572 to jclouds/jclouds
Building remotely on s-e17494b7 in workspace 

Fetching changes from the remote Git repository
Fetching upstream changes from git://github.com/jclouds/jclouds.git
  Opening connection
Done: 0
  Counting objects
Done: 33
  Finding sources
Done: 33
  Getting sizes
Done: 32
  Compressing objects
Done: 0
  Writing objects
Done: 33
  remote: Updating references
Merging refs/tags/changes/1790
FATAL: Could not merge AnyObjectId[00ae74577a3a7bb052d6683c669f740d9e0b1f50]
hudson.plugins.git.GitException: Could not merge 
AnyObjectId[00ae74577a3a7bb052d6683c669f740d9e0b1f50]
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:315)
at 
org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.merge(AbstractGitAPIImpl.java:63)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.merge(CliGitAPIImpl.java:47)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: hudson.plugins.git.GitException: Command "merge 
00ae74577a3a7bb052d6683c669f740d9e0b1f50" returned status code 1:
stdout: Auto-merging 
apis/openstack-nova/src/test/resources/extension_list_full.json
CONFLICT (content): Merge conflict in 
apis/openstack-nova/src/test/resources/extension_list_full.json
Auto-merging 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/extensions/ExtensionNamespaces.java
CONFLICT (content): Merge conflict in 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/extensions/ExtensionNamespaces.java
Automatic merge failed; fix conflicts and then commit the result.

stderr: 
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:928)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:909)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:853)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:863)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:313)
... 17 more

[jclouds] Support for OpenStack Services API (#572)

[Avi Ben-Harush]

You can merge this Pull Request by running:

  git pull https://github.com/avibh/jclouds-1 apache-1.8.x

Or you can view, comment on it, or merge it online at:

  https://github.com/jclouds/jclouds/pull/572

-- Commit Summary --

  * Support for OpenStack Services API

-- File Changes --

M 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/NovaApi.java 
(10)
M 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/config/NovaHttpApiModule.java
 (2)
A 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/domain/OsService.java
 (235)
M 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/extensions/ExtensionNamespaces.java
 (6)
A 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/extensions/OsServicesApi.java
 (93)
A 
apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/extensions/OsServicesApiExpectTest.java
 (79)
A 
apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/extensions/OsServicesApiLiveTest.java
 (93)
M apis/openstack-nova/src/test/resources/extension_list_full.json (8)
A apis/openstack-nova/src/test/resources/os_services_list.json (36)

-- Patch Links --

https://github.com/jclouds/jclouds/pull/572.patch
https://github.com/jclouds/jclouds/pull/572.diff

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/572

[jira] [Commented] (JCLOUDS-747) Determine level of android support and how to ensure we keep it.

[Adrian Cole (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168900#comment-14168900
 ] 

Adrian Cole commented on JCLOUDS-747:
-

I think we should move the "rollback java 7" topic back to JCLOUDS-652, and 
focus this on the android use case.

With regards to users requests there are no-brainers such as portably accessing 
storage.

Even without searching pre-ASF, we can ask those who have tried jclouds on 
android why they were, including the mail thread that started this issue.
http://apache.markmail.org/search/?q=jclouds%20android

Let's move this conversation towards the users, and remember that few users are 
even on the jclouds lists anymore, much less follow jclouds on twitter. The 
fact that we've gotten a few requests this year on android despite that is a 
signal that we should at least pay attention.

> Determine level of android support and how to ensure we keep it.
> 
>
> Key: JCLOUDS-747
> URL: https://issues.apache.org/jira/browse/JCLOUDS-747
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Reporter: Adrian Cole
>
> One of the knock-on effects of moving on is tracking how we deal with 
> android. One way is to establish a floor android level we aim to support 
> (even if it is best efforts). That's due to the fact that android != java and 
> only a subset of features are present, on each version. Here's a handy link 
> that begins to discuss this complexity.
> http://stackoverflow.com/questions/20480090/does-android-support-jdk-6-or-7
> Modern android libraries typically use a combination of plugins and 
> integration tests to ensure android isn't accidentally broken. Some projects 
> just rely on folks to remember the rules.
> Here's an example of a signature-checking plugin
> {code}
>   
> org.codehaus.mojo
> animal-sniffer-maven-plugin
> ${animal.sniffer.version}
> 
>   
> test
> 
>   check
> 
>   
> 
> 
>   
> org.codehaus.mojo.signature
> java16
> 1.1
>   
> 
>   
> {code}
> In short, I think we should be careful and consciously decide whether certain 
> features that break some level of android support are worthwhile. We should 
> also note that entrypoints that aren't used by android callers will not 
> affect compatibility. In other words, we are most concerned with the common 
> paths.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JCLOUDS-652) Transition to Java 7

[Adrian Cole (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168895#comment-14168895
 ] 

Adrian Cole commented on JCLOUDS-652:
-

As evident in mailing list discussion and also JCLOUDS-747 I suggest we roll 
this back.

We would document that those who are trying to use the default jclouds http 
service and try to send or receive >2GB in one chunk will fail. They should 
either use multipart upload, or another http driver that can accept a long. 
Since we've never released a version that supports larger than that out of the 
box, this is more us documenting that constraint and how to work around it.

Internally, we shouldn't proliferate try-with-resources, and in fact, should 
just change the language level back to 6.

Since we've done no feature work in 2.x, this is an easy rollback.

In the mean time, we can avoid the 2 branch of dev problem until we encounter 
something actually worth breaking over. For example, we can regularly cut 
releases from master without incompatible patch backporting.

I know that [~gaul] will highly object to this, so let's call a VOTE if that 
happens.

> Transition to Java 7
> 
>
> Key: JCLOUDS-652
> URL: https://issues.apache.org/jira/browse/JCLOUDS-652
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Affects Versions: 2.0.0
>Reporter: Andrew Gaul
>Assignee: Andrew Gaul
> Fix For: 2.0.0
>
>
> Moving to Java 7 allows jclouds to use more language and library features 
> such as try-with-resources and HTTP client improvements.  We previously 
> discussed dropping Java 6 support for jclouds 2.0 on the user mailing list:
> http://mail-archives.apache.org/mod_mbox/jclouds-user/201405.mbox/%3C20140528185718.GC1036@sherlock%3E
> We need to unhook the Java 6 CloudBees builders before committing the Maven 
> compile requirement.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: jclouds-cli #194

[jenkins-no-reply]

See 

--
[...truncated 256 lines...]
[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-java) @ 
jclouds-cli-branding ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
jclouds-cli-branding ---
[INFO] artifact com.google.guava:guava: checking for updates from central
[INFO] artifact com.google.guava:guava: checking for updates from 
cloudbees-private-release-repository
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
jclouds-cli-branding ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @ 
jclouds-cli-branding ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-bundle-plugin:2.1.0:manifest (bundle-manifest) @ 
jclouds-cli-branding ---
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
jclouds-cli-branding ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.0.2:testCompile (default-testCompile) @ 
jclouds-cli-branding ---
[INFO] No sources to compile
[WARNING] Failed to getClass for org.gaul.modernizer_maven_plugin.ModernizerMojo
[INFO] 
[INFO] --- modernizer-maven-plugin:1.1.0:modernizer (modernizer) @ 
jclouds-cli-branding ---
[INFO] 
[INFO] --- maven-install-plugin:2.4:install (default-install) @ 
jclouds-cli-branding ---
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/jclouds/cli/jclouds-cli-branding/2.0.0-SNAPSHOT/jclouds-cli-branding-2.0.0-SNAPSHOT.jar
[INFO] Installing 
 to 
/home/jenkins/.m2/repository/org/apache/jclouds/cli/jclouds-cli-branding/2.0.0-SNAPSHOT/jclouds-cli-branding-2.0.0-SNAPSHOT.pom
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/jclouds/cli/jclouds-cli-branding/2.0.0-SNAPSHOT/jclouds-cli-branding-2.0.0-SNAPSHOT-tests.jar
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/jclouds/cli/jclouds-cli-branding/2.0.0-SNAPSHOT/jclouds-cli-branding-2.0.0-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-bundle-plugin:2.1.0:install (default-install) @ 
jclouds-cli-branding ---
[INFO] Local OBR update disabled (enable with -DobrRepository)
[INFO] 
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ 
jclouds-cli-branding ---
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-branding/2.0.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-branding/2.0.0-SNAPSHOT/maven-metadata.xml
 (2 KB at 3.3 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-branding/2.0.0-SNAPSHOT/jclouds-cli-branding-2.0.0-20141013.014539-14.jar
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-branding/2.0.0-SNAPSHOT/jclouds-cli-branding-2.0.0-20141013.014539-14.jar
 (9 KB at 11.9 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-branding/2.0.0-SNAPSHOT/jclouds-cli-branding-2.0.0-20141013.014539-14.pom
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-branding/2.0.0-SNAPSHOT/jclouds-cli-branding-2.0.0-20141013.014539-14.pom
 (2 KB at 2.2 KB/sec)
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-branding/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-branding/maven-metadata.xml
 (302 B at 0.8 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-branding/2.0.0-SNAPSHOT/maven-metadata.xml
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-branding/2.0.0-SNAPSHOT/maven-metadata.xml
 (2 KB at 1.9 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-branding/maven-m

Re: [jclouds] Fix GuiceAssistedInjectScoping error-prone warning (#571)

[Andrew Phillips]

> As suggested in the commit message, error-prone emitted this warning

Ahh...sorry, didn't get that first time around ;-) Thanks for explaining!

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/571#issuecomment-58834497

Re: [jclouds-karaf] Removing features related to stale providers (#56)

[Andrew Phillips]

Closed #56.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/56#event-177452377

[jira] [Commented] (JCLOUDS-735) Remove ninefold providers

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168882#comment-14168882
 ] 

ASF subversion and git services commented on JCLOUDS-735:
-

Commit 75040ea6eadd73010960614ca3c6c82bbadc2dc7 in jclouds-karaf's branch 
refs/heads/master from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-karaf.git;h=75040ea ]

Catching up with provider removal in jclouds core

* bluelock-vcloud-zone01 (7e04f62)
* greenhousedata-element-vcloud (0acc61b)
* JCLOUDS-735: ninefold-storage (1d95d29) and ninefold-compute (1d95d29)

Also adding cloudstack as a feature explicitly since it's no longer
transitively included via ninefold-compute


> Remove ninefold providers
> -
>
> Key: JCLOUDS-735
> URL: https://issues.apache.org/jira/browse/JCLOUDS-735
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-core
>Reporter: Adrian Cole
> Fix For: 1.8.1
>
>
> Ninefold's compute and storage and storage service is deprecated and they've 
> switched to rails hosting. Let's remove the providers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jclouds-karaf] Removing features related to stale providers (#56)

[Andrew Phillips]

Committed to 
[master](https://git-wip-us.apache.org/repos/asf?p=jclouds-karaf.git;a=commit;h=75040ea6eadd73010960614ca3c6c82bbadc2dc7)

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/56#issuecomment-58833702

[jira] [Commented] (JCLOUDS-692) Remove the CloudSigma v1 provider

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168880#comment-14168880
 ] 

ASF subversion and git services commented on JCLOUDS-692:
-

Commit 59eda397b7574f0602d1311bf356148b347eb67d in jclouds-karaf's branch 
refs/heads/master from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-karaf.git;h=59eda39 ]

JCLOUDS-692: Removing CloudSigma v1 features

Follow-on from jclouds/jclouds commit f7aea987


> Remove the CloudSigma v1 provider
> -
>
> Key: JCLOUDS-692
> URL: https://issues.apache.org/jira/browse/JCLOUDS-692
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 1.8.0
>Reporter: Ignasi Barrera
>Assignee: Adrian Cole
> Fix For: 2.0.0
>
>
> The CloudSigma v1 API has been retired and now the only offering is its 
> version 2. The cloudsigma provider should be removed from the main repo, and 
> communicate that the cloudsigma2 provider in labs should be used instead.
> We should also consider renaming the CloudSigma2 in labs to CloudSigma.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JCLOUDS-742) Remove cloudonestorage provider

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168881#comment-14168881
 ] 

ASF subversion and git services commented on JCLOUDS-742:
-

Commit c8e5a3867804c8ffafc6e41784411c49840a1ac9 in jclouds-karaf's branch 
refs/heads/master from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-karaf.git;h=c8e5a38 ]

JCLOUDS-742: Removing cloudonestorage feature

Provider was removed in jclouds/jclouds commit 9df0cd24


> Remove cloudonestorage provider
> ---
>
> Key: JCLOUDS-742
> URL: https://issues.apache.org/jira/browse/JCLOUDS-742
> Project: jclouds
>  Issue Type: Task
>  Components: jclouds-core
>Reporter: Adrian Cole
>Assignee: Andrew Gaul
> Fix For: 1.8.1
>
>
> This metadata-only provider provides little value other than setting
> the endpoint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jclouds-labs] [JCLOUDS-702] JCloud ProfitBricks provider implementation (#72)

[Reijhanniel Jearl Campos]

Hi @demobox :

Q1: The company I am in uses PB as IaaS provider, and seeing that jclouds 
doesn't support PB yet, I created this PR. I wanted to contribute to an 
open-source project (my first actually. :D) which I told @nacx via email. I was 
interested in the concept of cloud provider abstraction which I 
initially saw in http://deltacloud.apache.org/";>deltacloud (ruby). 
But then, I'm a java-biased person and so here I am. :)
Q2: I don't exactly understand the question, but I'll continue to update 
this provider for quite a while - most likely in 2+ years depending with their 
frequency of API updates. 
Q3: Unfortunately, PB doesn't support testing accounts for dev (at 
least not yet). To get started with this PR, I requested a trial account. Since 
14 days is not enough, I emailed then http://www.linkedin.com/in/aarongarza";>Aaron Garza, VP Sales at 
ProfitBricks for an extension after describing this project. This PR's 
development so far runs in an extended-trial basis.

With that said, thanks for noticing :wink: this PR. I look forward to learning 
a lot more through this development. 

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/72#issuecomment-58833155

Jenkins build is back to stable : jclouds » jclouds #1789

[BuildHive]

See 

Jenkins build is back to normal : jclouds-karaf #724

[jenkins-no-reply]

See 

Jenkins build became unstable: jclouds » jclouds #1788

[BuildHive]

See 

Build failed in Jenkins: jclouds-karaf #723

[jenkins-no-reply]

See 

--
[...truncated 133 lines...]
Downloading: 
https://repository-jclouds.forge.cloudbees.com/snapshot/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://oss.sonatype.org/content/repositories/releases/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/maven-metadata.xml
 (999 B at 5.1 KB/sec)
Downloaded: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/maven-metadata.xml
 (999 B at 5.1 KB/sec)
Downloading: 
https://repository-jclouds.forge.cloudbees.com/snapshot/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/jclouds-compute-2.0.0-20141012.234435-82.pom
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/jclouds-compute-2.0.0-20141012.234435-82.pom
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/jclouds-compute-2.0.0-20141012.234435-82.pom
 (3 KB at 14.6 KB/sec)
Downloading: 
http://download.java.net/maven/2/org/apache/jclouds/jclouds-scriptbuilder/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://oss.sonatype.org/content/repositories/releases/org/apache/jclouds/jclouds-scriptbuilder/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://repository-jclouds.forge.cloudbees.com/snapshot/org/apache/jclouds/jclouds-scriptbuilder/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-scriptbuilder/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-scriptbuilder/2.0.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-scriptbuilder/2.0.0-SNAPSHOT/maven-metadata.xml
 (1005 B at 5.1 KB/sec)
Downloaded: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-scriptbuilder/2.0.0-SNAPSHOT/maven-metadata.xml
 (1005 B at 5.1 KB/sec)
Downloading: 
https://repository-jclouds.forge.cloudbees.com/snapshot/org/apache/jclouds/jclouds-scriptbuilder/2.0.0-SNAPSHOT/jclouds-scriptbuilder-2.0.0-20141012.234344-83.pom
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-scriptbuilder/2.0.0-SNAPSHOT/jclouds-scriptbuilder-2.0.0-20141012.234344-83.pom
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-scriptbuilder/2.0.0-SNAPSHOT/jclouds-scriptbuilder-2.0.0-20141012.234344-83.pom
 (4 KB at 17.6 KB/sec)
Downloading: 
https://repository-jclouds.forge.cloudbees.com/snapshot/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://oss.sonatype.org/content/repositories/releases/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://download.java.net/maven/2/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
 (1001 B at 5.0 KB/sec)
Downloaded: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
 (1001 B at 5.2 KB/sec)
Downloading: 
https://repository-jclouds.forge.cloudbees.com/snapshot/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/jclouds-blobstore-2.0.0-20141012.234746-82.pom
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/jclouds-blobstore-2.0.0-20141012.234746-82.pom
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/jclouds-blobstore-2.0.0-20141012.234746-82.pom
 (4 KB at 18.1 KB/sec)
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-core/2.0.0-SNAPSHOT/jclouds-core-2.0.0-20141012.234247-83.jar
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/jclouds-compute-2.0.0-20141012.234435-82.jar
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/jclouds-blobstore-2.0.0-20141012.234746-82.jar
Downloading: 
https:/

[jira] [Commented] (JCLOUDS-747) Determine level of android support and how to ensure we keep it.

[Chris Custine (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168851#comment-14168851
 ] 

Chris Custine commented on JCLOUDS-747:
---

I agree that we should at least stop the door from slamming on potential 
Android development even if we have nothing concrete going right now.  I know 
several people on the project have talked about wanting to work on this for 
some time now, so I think we should give it a fighting chance. As I said in my 
email, I think this subject is fairly well documented wrt language features and 
sdk versions so it shouldn't be too difficult to draw up some guidelines on 
maintaining Android compatibility.

> Determine level of android support and how to ensure we keep it.
> 
>
> Key: JCLOUDS-747
> URL: https://issues.apache.org/jira/browse/JCLOUDS-747
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Reporter: Adrian Cole
>
> One of the knock-on effects of moving on is tracking how we deal with 
> android. One way is to establish a floor android level we aim to support 
> (even if it is best efforts). That's due to the fact that android != java and 
> only a subset of features are present, on each version. Here's a handy link 
> that begins to discuss this complexity.
> http://stackoverflow.com/questions/20480090/does-android-support-jdk-6-or-7
> Modern android libraries typically use a combination of plugins and 
> integration tests to ensure android isn't accidentally broken. Some projects 
> just rely on folks to remember the rules.
> Here's an example of a signature-checking plugin
> {code}
>   
> org.codehaus.mojo
> animal-sniffer-maven-plugin
> ${animal.sniffer.version}
> 
>   
> test
> 
>   check
> 
>   
> 
> 
>   
> org.codehaus.mojo.signature
> java16
> 1.1
>   
> 
>   
> {code}
> In short, I think we should be careful and consciously decide whether certain 
> features that break some level of android support are worthwhile. We should 
> also note that entrypoints that aren't used by android callers will not 
> affect compatibility. In other words, we are most concerned with the common 
> paths.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JCLOUDS-747) Determine level of android support and how to ensure we keep it.

[Andrew Gaul (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168845#comment-14168845
 ] 

Andrew Gaul commented on JCLOUDS-747:
-

[~nacx] We circulated the the Java 7 proposal on the user mailing list, not the 
development list, and we publicized it via Twitter as well.

[~adriancole] Android API level 19 supports many of the Java 7 features we 
propose using, including try-with-resources and 
{{HttpUrlConnection.setFixedLengthStreamingMode(long)}}, although not 
filesystem extended attributes.  Roughly 25% of devices support this today, 
trending upward and presumably higher when jclouds 2.0 releases.

More generally, what use case do we envision for jclouds users on mobile 
devices?  Do owners of older phones overlap with this?  Are we comfortable with 
a small and hypothetical user base with no known projects determining the 
requirements for the larger user base?  I strongly believe someone creating a 
mobile cloud application should explain their needs to us instead of guessing 
at what they might be.

> Determine level of android support and how to ensure we keep it.
> 
>
> Key: JCLOUDS-747
> URL: https://issues.apache.org/jira/browse/JCLOUDS-747
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Reporter: Adrian Cole
>
> One of the knock-on effects of moving on is tracking how we deal with 
> android. One way is to establish a floor android level we aim to support 
> (even if it is best efforts). That's due to the fact that android != java and 
> only a subset of features are present, on each version. Here's a handy link 
> that begins to discuss this complexity.
> http://stackoverflow.com/questions/20480090/does-android-support-jdk-6-or-7
> Modern android libraries typically use a combination of plugins and 
> integration tests to ensure android isn't accidentally broken. Some projects 
> just rely on folks to remember the rules.
> Here's an example of a signature-checking plugin
> {code}
>   
> org.codehaus.mojo
> animal-sniffer-maven-plugin
> ${animal.sniffer.version}
> 
>   
> test
> 
>   check
> 
>   
> 
> 
>   
> org.codehaus.mojo.signature
> java16
> 1.1
>   
> 
>   
> {code}
> In short, I think we should be careful and consciously decide whether certain 
> features that break some level of android support are worthwhile. We should 
> also note that entrypoints that aren't used by android callers will not 
> affect compatibility. In other words, we are most concerned with the common 
> paths.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jclouds] Fix GuiceAssistedInjectScoping error-prone warning (#571)

[Andrew Gaul]

As suggested in the commit message, error-prone emitted this warning.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/571#issuecomment-58826390

Re: [jclouds] Fix GuiceAssistedInjectScoping error-prone warning (#571)

[Andrew Phillips]

+1 - looks good to me too. Thanks, @andrewgaul!

Is this a pattern we could add to Checkstyle and/or something like error-prone? 
It seems like `@Singleton` and `@Assisted` shouldn't appear in the same class?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/571#issuecomment-58826087

Re: [jclouds] Fix GuiceAssistedInjectScoping error-prone warning (#571)

[Andrew Gaul]

Pushed to master as 489850d7db58552a1181672111c035ebd116cc4d.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/571#issuecomment-58825959

Re: [jclouds-labs-google] Implemented the supports exclusion CIDR new method (#57)

[Andrew Phillips]

> @@ -321,6 +321,11 @@ public boolean supportsPortRangesForGroups() {
>return true;
> }
>  
> +   @Override
> +   public boolean supportsExclusionCidrBlocks() {
> +   return false;

Thanks for fixing the indent, @nacx ;-)

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/57/files#r18750890

[jira] [Commented] (JCLOUDS-747) Determine level of android support and how to ensure we keep it.

[Adrian Cole (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168833#comment-14168833
 ] 

Adrian Cole commented on JCLOUDS-747:
-

So, I don't do android fulltime, but I have worked on an android app this year 
at my dayjob, specifically a component that synchronized a local model to an 
http endpoint. I also contribute to android libraries that end up in AOSP.

I would say that the java7 question this isn't a slam dunk, it is more about 
being able to play at all. 

Android in real life can't depend on the latest api version, as it just isn't 
deployed. Android in real life may encounter other problems, including the 
heaviness of jclouds with regards to initialization, reflection, allocation, 
scheduling etc.

However, those issues are easier to solve than making the world deploy the 
latest android release.

This in mind, if we continue to run master on java 7, we are basically formally 
closing the android door. People who have interest in android would probably 
look at maybe adapting other frameworks to read jclouds interfaces, or just 
recreate them in a different codebase.

I'd consider that a shame, as basically we would be trading these contributors 
for being able to use try-with-resources internally. Moreover, if an alternate 
framework rises out of this, and it ends up better, we'd have lost over 
try-with-resources.

> Determine level of android support and how to ensure we keep it.
> 
>
> Key: JCLOUDS-747
> URL: https://issues.apache.org/jira/browse/JCLOUDS-747
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Reporter: Adrian Cole
>
> One of the knock-on effects of moving on is tracking how we deal with 
> android. One way is to establish a floor android level we aim to support 
> (even if it is best efforts). That's due to the fact that android != java and 
> only a subset of features are present, on each version. Here's a handy link 
> that begins to discuss this complexity.
> http://stackoverflow.com/questions/20480090/does-android-support-jdk-6-or-7
> Modern android libraries typically use a combination of plugins and 
> integration tests to ensure android isn't accidentally broken. Some projects 
> just rely on folks to remember the rules.
> Here's an example of a signature-checking plugin
> {code}
>   
> org.codehaus.mojo
> animal-sniffer-maven-plugin
> ${animal.sniffer.version}
> 
>   
> test
> 
>   check
> 
>   
> 
> 
>   
> org.codehaus.mojo.signature
> java16
> 1.1
>   
> 
>   
> {code}
> In short, I think we should be careful and consciously decide whether certain 
> features that break some level of android support are worthwhile. We should 
> also note that entrypoints that aren't used by android callers will not 
> affect compatibility. In other words, we are most concerned with the common 
> paths.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jclouds] Fix GuiceAssistedInjectScoping error-prone warning (#571)

[BuildHive]

[jclouds » jclouds 
#1787](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1787/) 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/jclouds/jclouds/pull/571#issuecomment-58825199

Re: [jclouds-labs] Minor Docker Fixes (#89)

[Ignasi Barrera]

>@grkvlt Do you think it makes sense to wait for the image cache @nacx talks 
>about?

I think there is no need to block this PR until the image cache is refactored. 
The refactor will mitigate the side-effects that appear now when listing 
images, but I don't see these side-effects as blockers for other changes to be 
merged. I'd say to go ahead and merge this PR once the tests are completed.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/89#issuecomment-58824314

Re: [jclouds-labs] Add vSphere support (#61)

[Rob Schoening]

Getting a working working, supported vSphere support is very compelling for 
doing integration and automation in environments that have no IaaS 
support...which is most vCenter deployments.  

The vSphere API is extremely complicated and unpleasant to use.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-58824241

Jenkins build became unstable: jclouds-karaf #722

[jenkins-no-reply]

See 

[jira] [Commented] (JCLOUDS-747) Determine level of android support and how to ensure we keep it.

[Ignasi Barrera (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168806#comment-14168806
 ] 

Ignasi Barrera commented on JCLOUDS-747:


I'm definitely not an Android expert, but I think we should do our best to 
support it.

There was a discussion time ago about moving jclouds mater branch to Java 7. We 
all agreed and have been announcing that for a while, but If I'm not wrong no 
one took into account Android support. There weren't users/contributors 
stepping into the discussion and requesting that, but the participation in our 
dev@ list is often limited to the committers (I hope we improve this!). This 
is, we made the call to move to Java 7 without taking into account an important 
scenario.

The version of Java seems to be the conflicting part, and I think we should 
reconsider the decision by answering the following questions:

* What is more important for our users? Being able to use Java 7 features or 
being able to use jclouds on their Android devices?
* What will better help adoption? Will Java 7 make jclouds more attractive to 
people, or will Android bring more users and help us gain traction?
* What will make jclouds better?
* Why not Android? Is there a really good reason to not supporting (and not 
being able to support) Android?

These are the questions I ask myself when thinking about it, and I really think 
we should reconsider the Java7 thing and try to be Android friendly. We've 
already announced that we'll be supporting Java 7, but that shouldn't be a 
problem. We can announce that we've reconsidered that in favor of providing 
better support from Android. 

> Determine level of android support and how to ensure we keep it.
> 
>
> Key: JCLOUDS-747
> URL: https://issues.apache.org/jira/browse/JCLOUDS-747
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Reporter: Adrian Cole
>
> One of the knock-on effects of moving on is tracking how we deal with 
> android. One way is to establish a floor android level we aim to support 
> (even if it is best efforts). That's due to the fact that android != java and 
> only a subset of features are present, on each version. Here's a handy link 
> that begins to discuss this complexity.
> http://stackoverflow.com/questions/20480090/does-android-support-jdk-6-or-7
> Modern android libraries typically use a combination of plugins and 
> integration tests to ensure android isn't accidentally broken. Some projects 
> just rely on folks to remember the rules.
> Here's an example of a signature-checking plugin
> {code}
>   
> org.codehaus.mojo
> animal-sniffer-maven-plugin
> ${animal.sniffer.version}
> 
>   
> test
> 
>   check
> 
>   
> 
> 
>   
> org.codehaus.mojo.signature
> java16
> 1.1
>   
> 
>   
> {code}
> In short, I think we should be careful and consciously decide whether certain 
> features that break some level of android support are worthwhile. We should 
> also note that entrypoints that aren't used by android callers will not 
> affect compatibility. In other words, we are most concerned with the common 
> paths.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jclouds] Fix GuiceAssistedInjectScoping error-prone warning (#571)

[Adrian Cole]

+1 yeap we over-stamp singleton on things, and it makes no sense on a object 
returned from an assisted factory

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/571#issuecomment-58823392

Jenkins build is back to stable : jclouds-labs-openstack » jclouds rackspace-cloudfiles api #503

[jenkins-no-reply]

See 

Jenkins build is back to stable : jclouds-labs-openstack #503

[jenkins-no-reply]

See 

Re: [jclouds-karaf] Removing features related to stale providers (#56)

[BuildHive]

[jclouds » jclouds-karaf 
#1331](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-karaf/1331/) 
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/jclouds/jclouds-karaf/pull/56#issuecomment-58822990

Re: [jclouds] Fix GuiceAssistedInjectScoping error-prone warning (#571)

[CloudBees pull request builder plugin]

[jclouds-pull-requests 
#1286](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1286/) SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/571#issuecomment-58822878

[jira] [Commented] (JCLOUDS-752) Add error-prone to the build and create bug patterns for known bugs or anti-patterns.

[Adrian Cole (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168784#comment-14168784
 ] 

Adrian Cole commented on JCLOUDS-752:
-

OK, so sounds like we can address this with an activation profile until java8 
fix is in. Considering we have build checkers that use java7, this will be 
better than flying blind or just doing nothing.

> Add error-prone to the build and create bug patterns for known bugs or 
> anti-patterns.
> -
>
> Key: JCLOUDS-752
> URL: https://issues.apache.org/jira/browse/JCLOUDS-752
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Reporter: Adrian Cole
>
> We have bug patterns that regularly happen due to programming mistakes
>  * Having a fallback to null, but no nullable
>  * putting fallback with mismatching return type (ex. null on boolean)
>  * forgetting to add Named (which is used for timeout config)
> ...
> There's an existing tool, which was first published to maven central in may 
> 2012 and has had regular releases since, and contributions by several people: 
> Error prone
> error-prone allows you to use existing bug patterns or create new ones that 
> can help you identify bugs.
> https://code.google.com/p/error-prone/wiki/BugPatterns
> I'm aware that we already have checkstyle and modernizer in the build, and 
> [~gaul] is apprehensive about adding this. He mentioned a preference to run 
> it manually, and cited some concern about it not working with JDK 8 some time 
> ago.
> Instead of finding reasons not to use this tool, or limiting its 
> effectiveness to manual runs (which would allow new bugs to creep in), I 
> highly encourage us to be as fair with adding this as we were with adding 
> other tools like checkstyle and modernizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jclouds] Fix GuiceAssistedInjectScoping error-prone warning (#571)

[CloudBees pull request builder plugin]

[jclouds-pull-requests-java-6 
#197](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests-java-6/197/) 
SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/571#issuecomment-58821980

Jenkins build is back to normal : jclouds » jclouds-labs-google #1462

[BuildHive]

See 

Re: [jclouds] Fix GuiceAssistedInjectScoping error-prone warning (#571)

[Andrew Gaul]

I believe this is correct but would appreciate feedback from someone more 
experienced with Guice.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/571#issuecomment-58821953

[jclouds] Fix GuiceAssistedInjectScoping error-prone warning (#571)

[Andrew Gaul]

You can merge this Pull Request by running:

  git pull https://github.com/andrewgaul/jclouds error-prone-guice

Or you can view, comment on it, or merge it online at:

  https://github.com/jclouds/jclouds/pull/571

-- Commit Summary --

  * Fix GuiceAssistedInjectScoping error-prone warning

-- File Changes --

M 
apis/cloudstack/src/main/java/org/jclouds/cloudstack/functions/StaticNATVirtualMachineInNetwork.java
 (2)
M 
apis/openstack-keystone/src/main/java/org/jclouds/openstack/keystone/v2_0/suppliers/LocationIdToURIFromAccessForTypeAndVersion.java
 (2)
M 
apis/openstack-keystone/src/main/java/org/jclouds/openstack/keystone/v2_0/suppliers/RegionIdToAdminURIFromAccessForTypeAndVersion.java
 (2)
M 
apis/openstack-keystone/src/main/java/org/jclouds/openstack/keystone/v2_0/suppliers/RegionIdToURIFromAccessForTypeAndVersion.java
 (2)
M 
apis/openstack-keystone/src/main/java/org/jclouds/openstack/keystone/v2_0/suppliers/ZoneIdToURIFromAccessForTypeAndVersion.java
 (2)
M 
apis/rackspace-cloudidentity/src/main/java/org/jclouds/rackspace/cloudidentity/v1_1/suppliers/RegionIdToURIFromAuthForServiceSupplier.java
 (2)
M 
apis/rackspace-cloudidentity/src/main/java/org/jclouds/rackspace/cloudidentity/v1_1/suppliers/V1DefaultRegionIdSupplier.java
 (2)
M 
common/openstack/src/main/java/org/jclouds/openstack/functions/URIFromAuthenticationResponseForService.java
 (2)
M 
common/openstack/src/main/java/org/jclouds/openstack/keystone/v1_1/suppliers/RegionIdToURIFromAuthForServiceSupplier.java
 (2)
M 
common/openstack/src/main/java/org/jclouds/openstack/keystone/v1_1/suppliers/V1DefaultRegionIdSupplier.java
 (2)
M 
core/src/main/java/org/jclouds/location/suppliers/fromconfig/LocationIdToURIFromConfigurationOrDefaultToProvider.java
 (2)
M 
providers/aws-ec2/src/main/java/org/jclouds/aws/ec2/compute/suppliers/CallForImages.java
 (2)

-- Patch Links --

https://github.com/jclouds/jclouds/pull/571.patch
https://github.com/jclouds/jclouds/pull/571.diff

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/571

[jira] [Commented] (JCLOUDS-752) Add error-prone to the build and create bug patterns for known bugs or anti-patterns.

[Andrew Gaul (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168781#comment-14168781
 ] 

Andrew Gaul commented on JCLOUDS-752:
-

I experience these symptoms with 1.8.0_20:

{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on 
project jclouds-resources: Execution default-compile of goal 
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile failed: Plugin 
org.apache.maven.plugins:maven-compiler-plugin:3.1 or one of its dependencies 
could not be resolved: Failure to find 
com.google.errorprone:error_prone_jdk8:jar:1.1.2 in 
https://repo.maven.apache.org/maven2 was cached in the local repository, 
resolution will not be reattempted until the update interval of central has 
elapsed or updates are forced -> [Help 1]
{noformat}

Several upstream bugs report incompatibility with Java 8:

https://code.google.com/p/error-prone/issues/detail?id=246
https://code.google.com/p/error-prone/issues/detail?id=251

> Add error-prone to the build and create bug patterns for known bugs or 
> anti-patterns.
> -
>
> Key: JCLOUDS-752
> URL: https://issues.apache.org/jira/browse/JCLOUDS-752
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Reporter: Adrian Cole
>
> We have bug patterns that regularly happen due to programming mistakes
>  * Having a fallback to null, but no nullable
>  * putting fallback with mismatching return type (ex. null on boolean)
>  * forgetting to add Named (which is used for timeout config)
> ...
> There's an existing tool, which was first published to maven central in may 
> 2012 and has had regular releases since, and contributions by several people: 
> Error prone
> error-prone allows you to use existing bug patterns or create new ones that 
> can help you identify bugs.
> https://code.google.com/p/error-prone/wiki/BugPatterns
> I'm aware that we already have checkstyle and modernizer in the build, and 
> [~gaul] is apprehensive about adding this. He mentioned a preference to run 
> it manually, and cited some concern about it not working with JDK 8 some time 
> ago.
> Instead of finding reasons not to use this tool, or limiting its 
> effectiveness to manual runs (which would allow new bugs to creep in), I 
> highly encourage us to be as fair with adding this as we were with adding 
> other tools like checkstyle and modernizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (JCLOUDS-752) Add error-prone to the build and create bug patterns for known bugs or anti-patterns.

[Adrian Cole (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168780#comment-14168780
 ] 

Adrian Cole edited comment on JCLOUDS-752 at 10/12/14 8:36 PM:
---

[~gaul] have you raised an issue on "The way it hooks into javac is apparently 
invasive and fragile." or do you have an issue others raised we could track? 
The only one I can find that you commented on is this, which appears to have 
been marked resolved in january. 
https://code.google.com/p/error-prone/issues/detail?id=190

Do you have any fixes that aren't upstream?


was (Author: adriancole):
[~gaul] have you raised an issue on "The way it hooks into javac is apparently 
invasive and fragile." or do you have an issue others raised we could track? 
The only one I can find that you raised is this, which appears to have been 
marked resolved in january. 
https://code.google.com/p/error-prone/issues/detail?id=190

Do you have any fixes that aren't upstream?

> Add error-prone to the build and create bug patterns for known bugs or 
> anti-patterns.
> -
>
> Key: JCLOUDS-752
> URL: https://issues.apache.org/jira/browse/JCLOUDS-752
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Reporter: Adrian Cole
>
> We have bug patterns that regularly happen due to programming mistakes
>  * Having a fallback to null, but no nullable
>  * putting fallback with mismatching return type (ex. null on boolean)
>  * forgetting to add Named (which is used for timeout config)
> ...
> There's an existing tool, which was first published to maven central in may 
> 2012 and has had regular releases since, and contributions by several people: 
> Error prone
> error-prone allows you to use existing bug patterns or create new ones that 
> can help you identify bugs.
> https://code.google.com/p/error-prone/wiki/BugPatterns
> I'm aware that we already have checkstyle and modernizer in the build, and 
> [~gaul] is apprehensive about adding this. He mentioned a preference to run 
> it manually, and cited some concern about it not working with JDK 8 some time 
> ago.
> Instead of finding reasons not to use this tool, or limiting its 
> effectiveness to manual runs (which would allow new bugs to creep in), I 
> highly encourage us to be as fair with adding this as we were with adding 
> other tools like checkstyle and modernizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jenkins build is back to normal : jclouds-labs-google » jclouds Google Compute Engine provider #262

[jenkins-no-reply]

See 

Jenkins build is back to normal : jclouds-labs-google #262

[jenkins-no-reply]

See 

[jira] [Comment Edited] (JCLOUDS-752) Add error-prone to the build and create bug patterns for known bugs or anti-patterns.

[Adrian Cole (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168780#comment-14168780
 ] 

Adrian Cole edited comment on JCLOUDS-752 at 10/12/14 8:35 PM:
---

[~gaul] have you raised an issue on "The way it hooks into javac is apparently 
invasive and fragile." or do you have an issue others raised we could track? 
The only one I can find that you raised is this, which appears to have been 
marked resolved in january. 
https://code.google.com/p/error-prone/issues/detail?id=190

Do you have any fixes that aren't upstream?


was (Author: adriancole):
[~gaul] have you raised an issue on "The way it hooks into javac is apparently 
invasive and fragile." or do you have an issue others raised we could track?

> Add error-prone to the build and create bug patterns for known bugs or 
> anti-patterns.
> -
>
> Key: JCLOUDS-752
> URL: https://issues.apache.org/jira/browse/JCLOUDS-752
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Reporter: Adrian Cole
>
> We have bug patterns that regularly happen due to programming mistakes
>  * Having a fallback to null, but no nullable
>  * putting fallback with mismatching return type (ex. null on boolean)
>  * forgetting to add Named (which is used for timeout config)
> ...
> There's an existing tool, which was first published to maven central in may 
> 2012 and has had regular releases since, and contributions by several people: 
> Error prone
> error-prone allows you to use existing bug patterns or create new ones that 
> can help you identify bugs.
> https://code.google.com/p/error-prone/wiki/BugPatterns
> I'm aware that we already have checkstyle and modernizer in the build, and 
> [~gaul] is apprehensive about adding this. He mentioned a preference to run 
> it manually, and cited some concern about it not working with JDK 8 some time 
> ago.
> Instead of finding reasons not to use this tool, or limiting its 
> effectiveness to manual runs (which would allow new bugs to creep in), I 
> highly encourage us to be as fair with adding this as we were with adding 
> other tools like checkstyle and modernizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JCLOUDS-752) Add error-prone to the build and create bug patterns for known bugs or anti-patterns.

[Adrian Cole (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168780#comment-14168780
 ] 

Adrian Cole commented on JCLOUDS-752:
-

[~gaul] have you raised an issue on "The way it hooks into javac is apparently 
invasive and fragile." or do you have an issue others raised we could track?

> Add error-prone to the build and create bug patterns for known bugs or 
> anti-patterns.
> -
>
> Key: JCLOUDS-752
> URL: https://issues.apache.org/jira/browse/JCLOUDS-752
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Reporter: Adrian Cole
>
> We have bug patterns that regularly happen due to programming mistakes
>  * Having a fallback to null, but no nullable
>  * putting fallback with mismatching return type (ex. null on boolean)
>  * forgetting to add Named (which is used for timeout config)
> ...
> There's an existing tool, which was first published to maven central in may 
> 2012 and has had regular releases since, and contributions by several people: 
> Error prone
> error-prone allows you to use existing bug patterns or create new ones that 
> can help you identify bugs.
> https://code.google.com/p/error-prone/wiki/BugPatterns
> I'm aware that we already have checkstyle and modernizer in the build, and 
> [~gaul] is apprehensive about adding this. He mentioned a preference to run 
> it manually, and cited some concern about it not working with JDK 8 some time 
> ago.
> Instead of finding reasons not to use this tool, or limiting its 
> effectiveness to manual runs (which would allow new bugs to creep in), I 
> highly encourage us to be as fair with adding this as we were with adding 
> other tools like checkstyle and modernizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: jclouds » jclouds-labs-google #1461

[BuildHive]

See 

--
[...truncated 267 lines...]
[INFO] Exclude: **/README.txt
[INFO] Exclude: **/DEPENDENCIES
[INFO] Exclude: **/CONTRIBUTING.md
[INFO] Exclude: **/*json
[INFO] Exclude: **/*readme
[INFO] Exclude: **/test
[INFO] Exclude: **/test.pub
[INFO] Exclude: **/target/**
[INFO] Exclude: **/test-output/**
[INFO] Exclude: **/bin/**
[INFO] Exclude: **/.settings/**
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.dir-locals.el
[INFO] Exclude: **/.project
[INFO] Exclude: **/.idea/**
[INFO] Exclude: **/*.iml
[INFO] Exclude: **/*.eml
[INFO] Exclude: **/*.ipr
[INFO] Exclude: **/*.iws
[INFO] Exclude: **/*.DS_STORE
[INFO] Exclude: **/TAGS
[INFO] Exclude: **/.metadata/**
[INFO] Exclude: **/atlassian-ide-plugin.xml
[INFO] Exclude: **/.DS_Store
[INFO] Exclude: .mailmap
[INFO] Exclude: .git/**
[INFO] Exclude: **/.gitignore
[INFO] Exclude: **/.gitattributes
[INFO] Exclude: **/.java-version
[INFO] Exclude: **/modernizer_exclusions.txt
[INFO] Exclude: .repository/**
[INFO] Exclude: gc.log
[INFO] 46 resources included (use -debug for more details)
Warning:  org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
recognized.
Compiler warnings:
  WARNING:  'org.apache.xerces.jaxp.SAXParserImpl: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
Warning:  org.apache.xerces.parsers.SAXParser: Feature 
'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
Warning:  org.apache.xerces.parsers.SAXParser: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.
Warning:  org.apache.xerces.parsers.SAXParser: Property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
recognized.
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 
approved: 44 licence.
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ oauth ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (integration) @ oauth ---
[JENKINS] Recording test results[INFO] 
[INFO] --- maven-duplicate-finder-plugin:1.0.5:check (default) @ oauth ---

[INFO] Checking compile classpath
[INFO] Checking runtime classpath
[INFO] Checking test classpath
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.13:check (default) @ oauth ---
[INFO] 
[INFO] 
[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-banned-dependencies) @ 
oauth ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-java) @ oauth ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oauth ---
[INFO] artifact com.google.guava:guava: checking for updates from central
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ oauth ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ oauth ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
oauth ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ oauth 
---
[INFO] Nothing to compile - all classes are up to date
[WARNING] Failed to getClass for org.gaul.modernizer_maven_plugin.ModernizerMojo
[INFO] 
[INFO] --- modernizer-maven-plugin:1.1.0:modernizer (modernizer) @ oauth ---
[INFO] 
[INFO] 
[INFO] Building jclouds Google Compute Engine provider 2.0.0-SNAPSHOT
[INFO] 
Downloading: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/maven-metadata.xml
 (999 B at 3.3 KB/sec)
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/maven-metadata.xml
 (999 B at 2.6 KB/sec)
Downloading: 
htt

Re: [jclouds] Allow to configure CIDR exclusion blocks (#567)

[Ignasi Barrera]

> @@ -173,6 +173,54 @@ public void testRemoveIpPermission() {
> }
>  
> @Test(groups = { "integration", "live" }, singleThreaded = true, 
> dependsOnMethods = "testRemoveIpPermission")
> +   public void testAddIpPermissionWithCidrExclusionGroup() {
> +  skipIfSecurityGroupsNotSupported();
> +
> +  ComputeService computeService = view.getComputeService();
> +
> +  Optional securityGroupExtension = 
> computeService.getSecurityGroupExtension();
> +  assertTrue(securityGroupExtension.isPresent(), "security group 
> extension was not present");

I'm not sure why this is configured this way, but the skip method reads [this 
variable](https://github.com/jclouds/jclouds/blob/master/compute/src/test/java/org/jclouds/compute/extensions/internal/BaseSecurityGroupExtensionLiveTest.java#L67),
 which is not set by checking the presence of the extension. Seems like 
something that can be rethought and refactored in an upcoming PR.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/567/files#r18749900

[jira] [Commented] (JCLOUDS-752) Add error-prone to the build and create bug patterns for known bugs or anti-patterns.

[Andrew Gaul (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168779#comment-14168779
 ] 

Andrew Gaul commented on JCLOUDS-752:
-

I am actually not opposed to error-prone -- I have experimented with it, fixed 
its reported issues, and would advocate for it if it worked with Java 8 
runtimes.  The way it hooks into javac is apparently invasive and fragile.  
When upstream releases a version with a fix we can seriously consider 
error-prone.

> Add error-prone to the build and create bug patterns for known bugs or 
> anti-patterns.
> -
>
> Key: JCLOUDS-752
> URL: https://issues.apache.org/jira/browse/JCLOUDS-752
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Reporter: Adrian Cole
>
> We have bug patterns that regularly happen due to programming mistakes
>  * Having a fallback to null, but no nullable
>  * putting fallback with mismatching return type (ex. null on boolean)
>  * forgetting to add Named (which is used for timeout config)
> ...
> There's an existing tool, which was first published to maven central in may 
> 2012 and has had regular releases since, and contributions by several people: 
> Error prone
> error-prone allows you to use existing bug patterns or create new ones that 
> can help you identify bugs.
> https://code.google.com/p/error-prone/wiki/BugPatterns
> I'm aware that we already have checkstyle and modernizer in the build, and 
> [~gaul] is apprehensive about adding this. He mentioned a preference to run 
> it manually, and cited some concern about it not working with JDK 8 some time 
> ago.
> Instead of finding reasons not to use this tool, or limiting its 
> effectiveness to manual runs (which would allow new bugs to creep in), I 
> highly encourage us to be as fair with adding this as we were with adding 
> other tools like checkstyle and modernizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jenkins build is back to normal : jclouds » jclouds #1785

[BuildHive]

See 

Re: [jclouds] Allow to configure CIDR exclusion blocks (#567)

[Ignasi Barrera]

> @@ -217,6 +245,14 @@ public int getToPort() {
>return cidrBlocks;
> }
>  
> +   /**
> +* source of traffic is a all but this exclusionCidrBlocks

Yes!

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/567/files#r18749888

Re: [jclouds-labs-openstack] Adding copyFrom option to Glance (#163)

[BuildHive]

[jclouds » jclouds-labs-openstack 
#1845](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-openstack/1845/)
 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/jclouds/jclouds-labs-openstack/pull/163#issuecomment-58820789

Re: [jclouds-labs-openstack] Adding copyFrom option to Glance (#163)

[CloudBees pull request builder plugin]

[jclouds-labs-openstack-pull-requests 
#465](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/465/)
 SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/163#issuecomment-58820563

Jenkins build is back to normal : jclouds-karaf #721

[jenkins-no-reply]

See 

[jclouds-labs-openstack] Adding copyFrom option to Glance (#163)

[Andrew Phillips]

master version of https://github.com/jclouds/jclouds-labs-openstack/pull/162

/cc @inbarsto
You can merge this Pull Request by running:

  git pull https://github.com/jclouds/jclouds-labs-openstack add-copyimage

Or you can view, comment on it, or merge it online at:

  https://github.com/jclouds/jclouds-labs-openstack/pull/163

-- Commit Summary --

  * Adding copyFrom option to Glance

-- File Changes --

M 
openstack-glance/src/main/java/org/jclouds/openstack/glance/v1_0/options/CreateImageOptions.java
 (18)
M 
openstack-glance/src/test/java/org/jclouds/openstack/glance/v1_0/features/ImageApiExpectTest.java
 (23)
M 
openstack-glance/src/test/java/org/jclouds/openstack/glance/v1_0/features/ImageApiLiveTest.java
 (86)

-- Patch Links --

https://github.com/jclouds/jclouds-labs-openstack/pull/163.patch
https://github.com/jclouds/jclouds-labs-openstack/pull/163.diff

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/163

Re: [jclouds-karaf] Removing features related to stale providers (#56)

[Andrew Phillips]

Pushed this rebase because I was getting local test failures. Just want to 
verify before merging.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/56#issuecomment-58819668

Jenkins build became unstable: jclouds-labs-openstack » jclouds rackspace-cloudfiles api #502

[jenkins-no-reply]

See 

Jenkins build became unstable: jclouds-labs-openstack #502

[jenkins-no-reply]

See 

Re: [jclouds-karaf] Removing features related to stale providers (#56)

[CloudBees pull request builder plugin]

[jclouds-karaf-pull-requests 
#92](https://jclouds.ci.cloudbees.com/job/jclouds-karaf-pull-requests/92/) 
SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/56#issuecomment-58819291

Re: [jclouds-labs-openstack] openstack glance added option copy from to create image (#162)

[Andrew Phillips]

> Good to go?

Waiting for 1.8.1 (the 1.8.x branch is frozen right now). Just about to push a 
PR for master...

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/162#issuecomment-58819020

Build failed in Jenkins: jclouds-labs-google » jclouds Google Compute Engine provider #261

[jenkins-no-reply]

See 


--
[INFO] 
[INFO] 
[INFO] Building jclouds Google Compute Engine provider 2.0.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ google-compute-engine 
---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-banned-dependencies) @ 
google-compute-engine ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-java) @ 
google-compute-engine ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
google-compute-engine ---
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
google-compute-engine ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
google-compute-engine ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 100 source files to 

[INFO] -
[WARNING] COMPILATION WARNING : 
[INFO] -
[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 4 warnings 
[INFO] -
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
:[69,8]
 
org.jclouds.googlecomputeengine.compute.extensions.GoogleComputeEngineSecurityGroupExtension
 is not abstract and does not override abstract method 
supportsExclusionCidrBlocks() in 
org.jclouds.compute.extensions.SecurityGroupExtension
[INFO] 1 error
[INFO] -

Build failed in Jenkins: jclouds-labs-google #261

[jenkins-no-reply]

See 

--
[...truncated 2949 lines...]
[INFO] Exclude: **/README.txt
[INFO] Exclude: **/DEPENDENCIES
[INFO] Exclude: **/CONTRIBUTING.md
[INFO] Exclude: **/*json
[INFO] Exclude: **/*readme
[INFO] Exclude: **/test
[INFO] Exclude: **/test.pub
[INFO] Exclude: **/target/**
[INFO] Exclude: **/test-output/**
[INFO] Exclude: **/bin/**
[INFO] Exclude: **/.settings/**
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.dir-locals.el
[INFO] Exclude: **/.project
[INFO] Exclude: **/.idea/**
[INFO] Exclude: **/*.iml
[INFO] Exclude: **/*.eml
[INFO] Exclude: **/*.ipr
[INFO] Exclude: **/*.iws
[INFO] Exclude: **/*.DS_STORE
[INFO] Exclude: **/TAGS
[INFO] Exclude: **/.metadata/**
[INFO] Exclude: **/atlassian-ide-plugin.xml
[INFO] Exclude: **/.DS_Store
[INFO] Exclude: .mailmap
[INFO] Exclude: .git/**
[INFO] Exclude: **/.gitignore
[INFO] Exclude: **/.gitattributes
[INFO] Exclude: **/.java-version
[INFO] Exclude: **/modernizer_exclusions.txt
[INFO] Exclude: .repository/**
[INFO] Exclude: gc.log
[INFO] 46 resources included (use -debug for more details)
Warning:  org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
recognized.
Compiler warnings:
  WARNING:  'org.apache.xerces.jaxp.SAXParserImpl: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
Warning:  org.apache.xerces.parsers.SAXParser: Feature 
'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
Warning:  org.apache.xerces.parsers.SAXParser: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.
Warning:  org.apache.xerces.parsers.SAXParser: Property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
recognized.
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 
approved: 44 licence.
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ oauth ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-javadoc-plugin:2.9:aggregate-jar (javadoc) @ oauth ---
[INFO] 
[INFO] --- maven-javadoc-plugin:2.9:jar (javadoc) @ oauth ---
[INFO] 
5 warnings
[WARNING] Javadoc Warnings
[WARNING] 
:35:
 warning - Tag @link: reference not found: ApiMetadata
[WARNING] 
:152:
 warning - @returns is an unknown tag.
[WARNING] 
:35:
 warning - Tag @link: reference not found: ApiMetadata
[WARNING] 
:35:
 warning - Tag @link: reference not found: ApiMetadata
[WARNING] 
:35:
 warning - Tag @link: reference not found: ApiMetadata
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-source-plugin:2.2:jar-no-fork (attach-sources) @ oauth ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (integration) @ oauth ---
[JENKINS] Recording test results[INFO] 
[INFO] --- maven-duplicate-finder-plugin:1.0.5:check (default) @ oauth ---

[INFO] Checking compile classpath
[INFO] Checking runtime classpath
[INFO] Checking test classpath
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.13:check (default) @ oauth ---
[INFO] 
[INFO] 
[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-banned-dependencies) @ 
oauth ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-java) @ oauth ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oauth ---
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ oauth ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ oauth ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
oauth ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
<

Build failed in Jenkins: jclouds » jclouds #1784

[BuildHive]

See 

--
GitHub pull request #570 to jclouds/jclouds
Building remotely on s-7f29 in workspace 

Fetching changes from the remote Git repository
Fetching upstream changes from git://github.com/jclouds/jclouds.git
  Opening connection
Done: 0
  Counting objects
Done: 4658
  Finding sources
Done: 4658
  Getting sizes
Done: 2625
  Compressing objects
Done: 424212
  Writing objects
Done: 4658
  remote: Resolving deltas
  remote: Updating references
Merging refs/tags/changes/1784
FATAL: Could not merge AnyObjectId[e6f371c10d9c1d93415347a88ca76ca62524085b]
hudson.plugins.git.GitException: Could not merge 
AnyObjectId[e6f371c10d9c1d93415347a88ca76ca62524085b]
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:315)
at 
org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.merge(AbstractGitAPIImpl.java:63)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.merge(CliGitAPIImpl.java:47)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: hudson.plugins.git.GitException: Command "merge 
e6f371c10d9c1d93415347a88ca76ca62524085b" returned status code 1:
stdout: Auto-merging 
apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/parse/ParseFloatingIPPoolListTest.java
CONFLICT (add/add): Merge conflict in 
apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/parse/ParseFloatingIPPoolListTest.java
Auto-merging 
apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/extensions/FloatingIPPoolApiLiveTest.java
CONFLICT (add/add): Merge conflict in 
apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/extensions/FloatingIPPoolApiLiveTest.java
Auto-merging 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/extensions/FloatingIPPoolApi.java
CONFLICT (add/add): Merge conflict in 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/extensions/FloatingIPPoolApi.java
Auto-merging 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/domain/FloatingIPPool.java
CONFLICT (add/add): Merge conflict in 
apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/domain/FloatingIPPool.java
Automatic merge failed; fix conflicts and then commit the result.

stderr: 
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:928)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:909)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:853)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:863)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:313)
... 17 more

Re: [jclouds] Openstack nova list IP pools (#570)

[BuildHive]

[jclouds » jclouds 
#1784](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1784/) FAILURE
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/jclouds/pull/570#issuecomment-58818528

Build failed in Jenkins: jclouds » jclouds-labs-google #1460

[BuildHive]

See 

--
[...truncated 264 lines...]
[INFO] Exclude: **/LICENSE.txt
[INFO] Exclude: **/header.txt
[INFO] Exclude: **/NOTICE.txt
[INFO] Exclude: **/DISCLAIMER
[INFO] Exclude: **/BUILD.txt
[INFO] Exclude: **/CHANGES.txt
[INFO] Exclude: **/README.md
[INFO] Exclude: **/README.txt
[INFO] Exclude: **/DEPENDENCIES
[INFO] Exclude: **/CONTRIBUTING.md
[INFO] Exclude: **/*json
[INFO] Exclude: **/*readme
[INFO] Exclude: **/test
[INFO] Exclude: **/test.pub
[INFO] Exclude: **/target/**
[INFO] Exclude: **/test-output/**
[INFO] Exclude: **/bin/**
[INFO] Exclude: **/.settings/**
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.dir-locals.el
[INFO] Exclude: **/.project
[INFO] Exclude: **/.idea/**
[INFO] Exclude: **/*.iml
[INFO] Exclude: **/*.eml
[INFO] Exclude: **/*.ipr
[INFO] Exclude: **/*.iws
[INFO] Exclude: **/*.DS_STORE
[INFO] Exclude: **/TAGS
[INFO] Exclude: **/.metadata/**
[INFO] Exclude: **/atlassian-ide-plugin.xml
[INFO] Exclude: **/.DS_Store
[INFO] Exclude: .mailmap
[INFO] Exclude: .git/**
[INFO] Exclude: **/.gitignore
[INFO] Exclude: **/.gitattributes
[INFO] Exclude: **/.java-version
[INFO] Exclude: **/modernizer_exclusions.txt
[INFO] Exclude: .repository/**
[INFO] Exclude: gc.log
[INFO] 46 resources included (use -debug for more details)
Warning:  org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
recognized.
Compiler warnings:
  WARNING:  'org.apache.xerces.jaxp.SAXParserImpl: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
Warning:  org.apache.xerces.parsers.SAXParser: Feature 
'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
Warning:  org.apache.xerces.parsers.SAXParser: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.
Warning:  org.apache.xerces.parsers.SAXParser: Property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
recognized.
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 
approved: 44 licence.
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ oauth ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (integration) @ oauth ---
[JENKINS] Recording test results[INFO] 
[INFO] --- maven-duplicate-finder-plugin:1.0.5:check (default) @ oauth ---

[INFO] Checking compile classpath
[INFO] Checking runtime classpath
[INFO] Checking test classpath
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.13:check (default) @ oauth ---
[INFO] 
[INFO] 
[INFO] >>> modernizer-maven-plugin:1.1.0:modernizer (modernizer) @ oauth >>>
[INFO] 
[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-banned-dependencies) @ 
oauth ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-java) @ oauth ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oauth ---
[INFO] artifact com.google.guava:guava: checking for updates from central
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ oauth ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ oauth ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
oauth ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ oauth 
---
[INFO] Nothing to compile - all classes are up to date
[WARNING] Failed to getClass for org.gaul.modernizer_maven_plugin.ModernizerMojo
[INFO] 
[INFO] <<< modernizer-maven-plugin:1.1.0:modernizer (modernizer) @ oauth <<<
[INFO] 
[INFO] --- modernizer-maven-plugin:1.1.0:modernizer (modernizer) @ oauth ---
[INFO] 
[INFO] 
[INFO] Building jclouds Google Compute Engine provider 2.0.0-SNAPSHOT
[INFO] 
[INFO] Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/maven-metadata.xml
[INFO] Downloading: 
http://repository.apache.org/snapshots/or

Re: [jclouds-labs-openstack] openstack glance added option copy from to create image (#162)

[inbar stolberg]

Good to go?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/162#issuecomment-58818196

Re: [jclouds-karaf] Removing features related to stale providers (#56)

[BuildHive]

[jclouds » jclouds-karaf 
#1329](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-karaf/1329/) 
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/jclouds/jclouds-karaf/pull/56#issuecomment-58818099

Re: [jclouds] Openstack nova list IP pools (#570)

[BuildHive]

[jclouds » jclouds 
#1783](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1783/) 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/jclouds/jclouds/pull/570#issuecomment-58817918

Re: [jclouds] Openstack nova list IP pools (#570)

[inbar stolberg]

Thanks :) :+1: 

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/570#issuecomment-58817814

[jira] [Commented] (JCLOUDS-742) Remove cloudonestorage provider

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168759#comment-14168759
 ] 

ASF subversion and git services commented on JCLOUDS-742:
-

Commit c8e5a3867804c8ffafc6e41784411c49840a1ac9 in jclouds-karaf's branch 
refs/heads/rem-cloudsigma from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-karaf.git;h=c8e5a38 ]

JCLOUDS-742: Removing cloudonestorage feature

Provider was removed in jclouds/jclouds commit 9df0cd24


> Remove cloudonestorage provider
> ---
>
> Key: JCLOUDS-742
> URL: https://issues.apache.org/jira/browse/JCLOUDS-742
> Project: jclouds
>  Issue Type: Task
>  Components: jclouds-core
>Reporter: Adrian Cole
>Assignee: Andrew Gaul
> Fix For: 1.8.1
>
>
> This metadata-only provider provides little value other than setting
> the endpoint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JCLOUDS-735) Remove ninefold providers

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168760#comment-14168760
 ] 

ASF subversion and git services commented on JCLOUDS-735:
-

Commit 75040ea6eadd73010960614ca3c6c82bbadc2dc7 in jclouds-karaf's branch 
refs/heads/rem-cloudsigma from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-karaf.git;h=75040ea ]

Catching up with provider removal in jclouds core

* bluelock-vcloud-zone01 (7e04f62)
* greenhousedata-element-vcloud (0acc61b)
* JCLOUDS-735: ninefold-storage (1d95d29) and ninefold-compute (1d95d29)

Also adding cloudstack as a feature explicitly since it's no longer
transitively included via ninefold-compute


> Remove ninefold providers
> -
>
> Key: JCLOUDS-735
> URL: https://issues.apache.org/jira/browse/JCLOUDS-735
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-core
>Reporter: Adrian Cole
> Fix For: 1.8.1
>
>
> Ninefold's compute and storage and storage service is deprecated and they've 
> switched to rails hosting. Let's remove the providers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JCLOUDS-692) Remove the CloudSigma v1 provider

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168758#comment-14168758
 ] 

ASF subversion and git services commented on JCLOUDS-692:
-

Commit 59eda397b7574f0602d1311bf356148b347eb67d in jclouds-karaf's branch 
refs/heads/rem-cloudsigma from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-karaf.git;h=59eda39 ]

JCLOUDS-692: Removing CloudSigma v1 features

Follow-on from jclouds/jclouds commit f7aea987


> Remove the CloudSigma v1 provider
> -
>
> Key: JCLOUDS-692
> URL: https://issues.apache.org/jira/browse/JCLOUDS-692
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 1.8.0
>Reporter: Ignasi Barrera
>Assignee: Adrian Cole
> Fix For: 2.0.0
>
>
> The CloudSigma v1 API has been retired and now the only offering is its 
> version 2. The cloudsigma provider should be removed from the main repo, and 
> communicate that the cloudsigma2 provider in labs should be used instead.
> We should also consider renaming the CloudSigma2 in labs to CloudSigma.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jclouds-labs-openstack] openstack glance added option copy from to create image (#162)

[Andrew Phillips]

> i don't believe they are this PR related...

You're right - they're related to the ongoing 1.8.1 release (1.8.x is currently 
pointing to a not-yet-published 1.8.1 parent POM).

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/162#issuecomment-58817573

Re: [jclouds] Openstack nova list IP pools (6b83679)

[Andrew Phillips]

@inbarsto Please check if this modified version of the original test makes 
sense. The idea is that `regions` can be [limited to a single 
region](https://github.com/jclouds/jclouds/blob/master/apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/internal/BaseNovaApiLiveTest.java#L62-L68)
 if you wish, but will default to all regions otherwise.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/commit/6b83679ca4058455ea5cd05ecbe9f67fa75fc74a#commitcomment-8129754

Re: [jclouds] Openstack nova list IP pools (#570)

[Andrew Phillips]

Closed #570.

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

Re: [jclouds] Openstack nova list IP pools (#570)

[Andrew Phillips]

Committed to 
[master](https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=6b83679ca4058455ea5cd05ecbe9f67fa75fc74a)

Yayayyayaay!!

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/570#issuecomment-58816691

Re: [jclouds-karaf] Removing features related to stale providers (#56)

[BuildHive]

[jclouds » jclouds-karaf 
#1328](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-karaf/1328/) 
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/jclouds/jclouds-karaf/pull/56#issuecomment-58815444

Re: [jclouds-cli] Listing features alphabetically in assembly (e7a6dce)

[Andrew Phillips]

Looking at this file after the rearrangement, it's clear that this is totally 
out of sync with [the Karaf feature 
POM](https://github.com/jclouds/jclouds-karaf/blob/master/feature/pom.xml#L107-L162).
 That may be intentional and OK, but I suspect not.

@iocanel @ccustine Could either of you shed some more light on this? Thanks!

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-cli/commit/e7a6dce1eb86ffaa047581eeb6acc837eba0629b#commitcomment-8129677

Re: [jclouds-cli] Aligning with feature cleanup in karaf (#21)

[CloudBees pull request builder plugin]

[jclouds-cli-pull-requests 
#29](https://jclouds.ci.cloudbees.com/job/jclouds-cli-pull-requests/29/) SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-cli/pull/21#issuecomment-58815246

Re: [jclouds-labs] Add vSphere support (#61)

[Andrew Phillips]

Hi @igreenfield !

Thanks for sticking with this for so long! I'd briefly like to step back from 
the code for a second and get a better understanding of the background to the 
PR:

* are you adding this based on user demand, or to provide a multi-cloud Java 
client for vSphere, or for some other reason?
* do you know what plans there are to help ensure this provider stays 
up-to-date in future?
* is there a chance of getting the jclouds team access to a testing instance 
and account so we can run live tests for this?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/61#issuecomment-58815213

Re: [jclouds-labs] BlobStore API for Orion based back-ends (#45)

[Andrew Phillips]

Hi @timur87!

Thanks for sticking with this for so long! I'd briefly like to step back from 
the code for a second and get a better understanding of the background to the 
PR:

* are you adding this based on user demand, or to provide a Java client, or for 
some other reason?
* do you know what plans there are to help ensure this provider stays 
up-to-date in future?
* I see discussion above about getting a live account to test this in future. 
Do you know if we can ensure that that account will remain active?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/45#issuecomment-58815151

Re: [jclouds-labs] [JCLOUDS-702] JCloud ProfitBricks provider implementation (#72)

[Andrew Phillips]

Hi @devcsrj!

Thanks for sticking with this for so long! I'd briefly like to step back from 
the code for a second and get a better understanding of the background to the 
PR:

* are you adding this based on user demand, or to provide a Java client, or for 
some other reason?
* do you know what plans there are to help ensure this provider stays 
up-to-date in future?
* is there a chance of getting the jclouds team access to a testing account so 
we can run live tests for this?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/72#issuecomment-58815059

Re: [jclouds-karaf] Removing features related to stale providers (#56)

[CloudBees pull request builder plugin]

[jclouds-karaf-pull-requests 
#91](https://jclouds.ci.cloudbees.com/job/jclouds-karaf-pull-requests/91/) 
SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/56#issuecomment-58814933

Build failed in Jenkins: jclouds » jclouds-labs-google #1459

[BuildHive]

See 

--
[...truncated 267 lines...]
[INFO] Exclude: **/README.txt
[INFO] Exclude: **/DEPENDENCIES
[INFO] Exclude: **/CONTRIBUTING.md
[INFO] Exclude: **/*json
[INFO] Exclude: **/*readme
[INFO] Exclude: **/test
[INFO] Exclude: **/test.pub
[INFO] Exclude: **/target/**
[INFO] Exclude: **/test-output/**
[INFO] Exclude: **/bin/**
[INFO] Exclude: **/.settings/**
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.dir-locals.el
[INFO] Exclude: **/.project
[INFO] Exclude: **/.idea/**
[INFO] Exclude: **/*.iml
[INFO] Exclude: **/*.eml
[INFO] Exclude: **/*.ipr
[INFO] Exclude: **/*.iws
[INFO] Exclude: **/*.DS_STORE
[INFO] Exclude: **/TAGS
[INFO] Exclude: **/.metadata/**
[INFO] Exclude: **/atlassian-ide-plugin.xml
[INFO] Exclude: **/.DS_Store
[INFO] Exclude: .mailmap
[INFO] Exclude: .git/**
[INFO] Exclude: **/.gitignore
[INFO] Exclude: **/.gitattributes
[INFO] Exclude: **/.java-version
[INFO] Exclude: **/modernizer_exclusions.txt
[INFO] Exclude: .repository/**
[INFO] Exclude: gc.log
[INFO] 46 resources included (use -debug for more details)
Warning:  org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
recognized.
Compiler warnings:
  WARNING:  'org.apache.xerces.jaxp.SAXParserImpl: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
Warning:  org.apache.xerces.parsers.SAXParser: Feature 
'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
Warning:  org.apache.xerces.parsers.SAXParser: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.
Warning:  org.apache.xerces.parsers.SAXParser: Property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
recognized.
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 
approved: 44 licence.
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ oauth ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (integration) @ oauth ---
[INFO] 
[INFO] --- maven-duplicate-finder-plugin:1.0.5:check (default) @ oauth ---
[INFO] Checking compile classpath
[JENKINS] Recording test results
[INFO] Checking runtime classpath
[INFO] Checking test classpath
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.13:check (default) @ oauth ---
[INFO] 
[INFO] 
[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-banned-dependencies) @ 
oauth ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-java) @ oauth ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oauth ---
[INFO] artifact com.google.guava:guava: checking for updates from central
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ oauth ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ oauth ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
oauth ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ oauth 
---
[INFO] Nothing to compile - all classes are up to date
[WARNING] Failed to getClass for org.gaul.modernizer_maven_plugin.ModernizerMojo
[INFO] 
[INFO] --- modernizer-maven-plugin:1.1.0:modernizer (modernizer) @ oauth ---
[INFO] 
[INFO] 
[INFO] Building jclouds Google Compute Engine provider 2.0.0-SNAPSHOT
[INFO] 
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/maven-metadata.xml
 (999 B at 2.9 KB/sec)
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-compute/2.0.0-SNAPSHOT/maven-metadata.xml
 (999 B at 2.2 KB/sec)
Downloading: 
htt

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

[BuildHive]

See 

Re: [jclouds] Openstack nova list IP pools (#570)

[BuildHive]

[jclouds » jclouds 
#1782](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1782/) 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/jclouds/jclouds/pull/570#issuecomment-58813854

Re: [jclouds-karaf] Removing features related to stale providers (#56)

[CloudBees pull request builder plugin]

[jclouds-karaf-pull-requests 
#90](https://jclouds.ci.cloudbees.com/job/jclouds-karaf-pull-requests/90/) 
ABORTED


---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/56#issuecomment-58813409

Re: [jclouds-labs-openstack] openstack glance added option copy from to create image (#162)

[inbar stolberg]

cloudbees having problems, i don't believe they are this PR related...





---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/162#issuecomment-58813374

Re: [jclouds] cinder availability zones api + list call implemented (#560)

[inbar stolberg]

>grin. Hopefully, an experience that changes things for the better - not just 
>for you, but for all contributors. So we all have something to be grateful to 
>you for ;-)

you guys are awesome jclouds community is gr8 :)
 
it is for 1.8 i'll be happy if it will land there and in master as well
if you want me to create a different PR for master thats ok too...

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/560#issuecomment-58813217

Re: [jclouds-labs-openstack] openstack glance added option copy from to create image (#162)

[CloudBees pull request builder plugin]

[jclouds-labs-openstack-pull-requests 
#464](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/464/)
 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-openstack/pull/162#issuecomment-58812860

Re: [jclouds-labs-openstack] openstack glance added option copy from to create image (#162)

[inbar stolberg]

fixed the test/s :grin:

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/162#issuecomment-58812856

Build failed in Jenkins: jclouds » jclouds-labs-openstack #1842

[BuildHive]

See 


Changes:

[inbar.stolberg] openstack glance added option copy from to create image

--
GitHub pull request #162 to jclouds/jclouds-labs-openstack
Building remotely on s-13c85d89 in workspace 

Fetching changes from the remote Git repository
Fetching upstream changes from 
git://github.com/jclouds/jclouds-labs-openstack.git
  Opening connection
Done: 0
  Counting objects
Done: 23
  Finding sources
Done: 23
  Getting sizes
Done: 22
  Compressing objects
Done: 0
  Writing objects
Done: 23
  remote: Updating references
Merging refs/tags/changes/1842
Checking out Revision d43f221a164c6fc754c57d6a97a6774898e1d445 (1.8.x)
Cleaning workspace
Resetting working tree
Parsing POMs
Failed to transfer Could not find artifact 
org.apache.jclouds:jclouds-project:pom:1.8.1 in central 
(http://repo.cloudbees.com/content/repositories/central)
ERROR: Failed to parse POMs
hudson.util.IOException2: remote file operation failed: 
 at 
hudson.remoting.Channel@59750703:s-13c85d89
at hudson.FilePath.act(FilePath.java:907)
at hudson.FilePath.act(FilePath.java:884)
at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:933)
at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:661)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566)
at hudson.model.Run.execute(Run.java:1665)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:246)
Caused by: hudson.remoting.ProxyException: 
hudson.maven.MavenModuleSetBuild$MavenExecutionException: 
org.apache.maven.project.ProjectBuildingException: Some problems were 
encountered while processing the POMs:
[FATAL] Non-resolvable parent POM: Could not find artifact 
org.apache.jclouds:jclouds-project:pom:1.8.1 in central 
(http://repo.cloudbees.com/content/repositories/central) and 
'parent.relativePath' points at wrong local POM @ line 23, column 11

at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1337)
at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1071)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2439)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: hudson.remoting.ProxyException: 
org.apache.maven.project.ProjectBuildingException: Some problems were 
encountered while processing the POMs:
[FATAL] Non-resolvable parent POM: Could not find artifact 
org.apache.jclouds:jclouds-project:pom:1.8.1 in central 
(http://repo.cloudbees.com/content/repositories/central) and 
'parent.relativePath' points at wrong local POM @ line 23, column 11

at 
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364)
at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361)
at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331)
at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1274)
... 10 more

Re: [jclouds-labs-openstack] openstack glance added option copy from to create image (#162)

[BuildHive]

[jclouds » jclouds-labs-openstack 
#1842](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-openstack/1842/)
 FAILURE
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/jclouds-labs-openstack/pull/162#issuecomment-58812823

Re: [jclouds-karaf] Removing features related to stale providers (#56)

[Andrew Phillips]

Reopened #56.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/56#event-177401379

Re: [jclouds-karaf] Removing features related to stale providers (#56)

[Andrew Phillips]

> jclouds-karaf-pull-requests #89 UNSTABLE

Not clear why [the CloudStack 
test](https://jclouds.ci.cloudbees.com/job/jclouds-karaf-pull-requests/org.apache.jclouds.karaf$itests/89/testReport/junit/org.jclouds.karaf.itests/ApisFeaturesInstallationTest/testCloudStackFeature_org_jclouds_karaf_itests_ApisFeaturesInstallationTest_testCloudStackFeature_KarafTestContainer_mvn_org_apache_karaf__apache_karaf__2_3_2__tar_gz_/)
 is failing here. Let's kick it again...

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/56#issuecomment-58812701

Re: [jclouds] Openstack nova list IP pools (#570)

[CloudBees pull request builder plugin]

[jclouds-pull-requests 
#1285](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1285/) SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/570#issuecomment-58812042