Re: [jclouds-labs] Profitbricks server api (#227)

[Reijhanniel Jearl Campos]

Hi! I tried to build this branch on my machine, although it throws a 
compilation error on Azure (might be because of updates from the jclouds core).

With jenkins build aside, it seems to be 
[failing](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/1003/org.apache.jclouds.labs$profitbricks-rest/console)
 because of:
```
[INFO] --- maven-checkstyle-plugin:2.15:check (default) @ profitbricks-rest ---
[WARNING] 
src/main/java/org/apache/jclouds/profitbricks/rest/ProfitBricksApiMetadata.java[27:15]
 (imports) UnusedImports: Unused import - 
org.jclouds.reflect.Reflection2.typeToken.
```
This "style check" complain is reproducible as well when running:
```
mvn checkstyle:checkstyle --quiet -Dcheckstyle.output.file=/dev/stdout 
-Dcheckstyle.output.format=plain
```
Let's see if this makes jenkins happy. :)

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

[jira] [Resolved] (JCLOUDS-943) Add google-cloud-storage and google-compute-engine to jclouds-karaf and jclouds-cli

[Ignasi Barrera (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCLOUDS-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ignasi Barrera resolved JCLOUDS-943.

   Resolution: Fixed
Fix Version/s: 2.0.0

> Add google-cloud-storage and google-compute-engine to jclouds-karaf and 
> jclouds-cli
> ---
>
> Key: JCLOUDS-943
> URL: https://issues.apache.org/jira/browse/JCLOUDS-943
> Project: jclouds
>  Issue Type: New Feature
>  Components: jclouds-cli, jclouds-karaf
>Affects Versions: 1.9.0
>Reporter: Andrew Gaul
>  Labels: google-cloud-storage, google-compute-engine
> Fix For: 2.0.0
>
>
> Needed for parity with other providers.



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

Jenkins build is back to normal : jclouds-guava-guice-compat » 18.0,3.0,OpenJDK 7 (latest) #82

[jenkins-no-reply]

See 

Jenkins build is back to normal : jclouds #3344

[jenkins-no-reply]

See 

Jenkins build is back to normal : jclouds » jclouds openstack-trove api #3344

[jenkins-no-reply]

See 

[jira] [Created] (JCLOUDS-1070) Consistently implement equals and hashCode in ResourceMetadata subclasses

[Ignasi Barrera (JIRA)]

Ignasi Barrera created JCLOUDS-1070:
---

 Summary: Consistently implement equals and hashCode in 
ResourceMetadata subclasses
 Key: JCLOUDS-1070
 URL: https://issues.apache.org/jira/browse/JCLOUDS-1070
 Project: jclouds
  Issue Type: Bug
  Components: jclouds-core
Affects Versions: 1.9.2
Reporter: Ignasi Barrera


Currently {{ResourceMetadata}} subclasses don't use all fields in their equals 
and hashCode methods. This can make sense given the nature of those objects, 
but can lead to unmet expectations for some users.

There has to be a statement of whether or not fields such as the metadata, 
tags, and so should be considered in equals/hashCode.



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

Build failed in Jenkins: jclouds-guava-guice-compat » 19.0-rc1,3.0,OpenJDK 7 (latest) #82

[jenkins-no-reply]

See 


Changes:

[Andrew Gaul] Delete single- and multi-part objects in Swift

--
[...truncated 30915 lines...]
Starting test 
testDelimiterList(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testDelimiterList(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 12ms
Test suite progress: tests succeeded: 59, failed: 0, skipped: 5.
Starting test 
testListContainerGetBlobSize(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testListContainerGetBlobSize(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 4ms
Test suite progress: tests succeeded: 60, failed: 0, skipped: 5.
Starting test 
testListContainerWithZeroMaxResults(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testListContainerWithZeroMaxResults(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 4ms
Test suite progress: tests succeeded: 61, failed: 0, skipped: 5.
Starting test 
testListMarkerAfterLastKey(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testListMarkerAfterLastKey(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 4ms
Test suite progress: tests succeeded: 62, failed: 0, skipped: 5.
Starting test 
containerExists(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
containerExists(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 2ms
Test suite progress: tests succeeded: 63, failed: 0, skipped: 5.
Starting test 
deleteContainerIfEmptyWithContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
*** allocated new container jenkins-blobstore6173924081117317223...
[TestNG] Test 
deleteContainerIfEmptyWithContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 failed.
Test suite progress: tests succeeded: 63, failed: 1, skipped: 5.
Starting test 
deleteContainerIfEmptyWithoutContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
*** allocated new container jenkins-blobstore-7827422307315574993...
[TestNG] Test 
deleteContainerIfEmptyWithoutContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 3ms
Test suite progress: tests succeeded: 64, failed: 1, skipped: 5.
Starting test 
deleteContainerWithContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
*** allocated new container jenkins-blobstore-3048624560760322216...
[TestNG] Test 
deleteContainerWithContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 4ms
Test suite progress: tests succeeded: 65, failed: 1, skipped: 5.
Starting test 
deleteContainerWithoutContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
*** allocated new container jenkins-blobstore7145796632651766312...
[TestNG] Test 
deleteContainerWithoutContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 3ms
Test suite progress: tests succeeded: 66, failed: 1, skipped: 5.
Starting test 
testDirectory(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testDirectory(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 skipped.
Test suite progress: tests succeeded: 66, failed: 1, skipped: 6.
Starting test 
testListContainer(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testListContainer(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 25ms
Test suite progress: tests succeeded: 67, failed: 1, skipped: 6.
Starting test 
testListContainerMarker(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testListContainerMarker(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 54ms
Test suite progress: tests succeeded: 68, failed: 1, skipped: 6.
Starting test 
testListContainerMaxResults(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testListContainerMaxResults(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 64ms
Test suite progress: tests succeeded: 69, failed: 1, skipped: 6.
Starting test 
testListContainerPrefix(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testListContainerPrefix(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 40ms
Test suite progress: tests succeeded: 70, failed: 1, skipped: 6.
Starting test 
testListRootUsesDelimiter(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 

Jenkins build is back to normal : jclouds-guava-guice-compat » 17.0,4.0,OpenJDK 7 (latest) #82

[jenkins-no-reply]

See 

Re: [jclouds] Consistently implement domain object methods (a3376d4)

[Ignasi Barrera]

I neither have a strong opinion on this. Regarding compute, I don't see the 
tags and metadata fields relevant to determine a node/image equality. Could it 
make sense to add then the user metadata just to the StorageMetadata subclasses?
In any case, I've opened 
[JCLOUDS-1070](https://issues.apache.org/jira/browse/JCLOUDS-1070) to track 
this.

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