[
https://issues.apache.org/jira/browse/JCLOUDS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14366972#comment-14366972
]
ASF GitHub Bot commented on JCLOUDS-178:
Github user asfgit closed the pull
There are a couple of problems with this.
When I compile I get the warning.
$ javac -classpath
jclouds-1.9.0-rc1/lib/*:src/main/java/:src/main/resources/
src/main/java/org/jclouds/examples/rackspace/*.java
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-examples/pull/71
-- Commit Summary --
* Updated Rackspace examples to 1.9.0
-- File Changes --
M rackspace/pom.xml (4)
M
Wire log?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/71#issuecomment-83020909
[
https://issues.apache.org/jira/browse/JCLOUDS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated JCLOUDS-857:
Attachment: log.txt
Tests fail due to Incorrect number of names on
[
https://issues.apache.org/jira/browse/JCLOUDS-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zack Shoylev reassigned JCLOUDS-856:
Assignee: Zack Shoylev
openstack-swift provider mangles blob names that end with slash
+ final String requestId = api().add(params);
+ assertTrue(operationSucceeded.apply(requestId), requestId);
+ }
+
+ @Test(dependsOnMethods = testCreate)
+ public void testUpdate() {
+ final UpdateAffinityGroupParams params =
UpdateAffinityGroupParams.builder().
+
Just a couple minors. lgtm! Thanks @ilgrosso. Once addressed we'll have to wait
until 1.9.0 is released to merge this.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/150#issuecomment-83163466
+ }
+
+ public void testDelete() throws Exception {
+ MockWebServer server = mockAzureManagementServer();
+ server.enqueue(requestIdResponse(request-3));
+
+ try {
+ final AffinityGroupApi api =
api(server.getUrl(/)).getAffinityGroupApi();
+
+
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an AS IS BASIS,
+ * WITHOUT WARRANTIES OR
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/708
-- Commit Summary --
* Deprecate Nova API for volumes in favour of Cinder API for volumes
-- File Changes --
M
Ah that @Deprecated @Beta. Looks good though, +1.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/708#issuecomment-83239263
I'm not familiar with jclouds idioms, but it feels more natural to me to have
the `deleteAsset` and `deleteAssets` methods be defined in the [Service
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-labs-openstack/pull/182
-- Commit Summary --
* Allows manually deleting (purging) cached CDN assets
-- File Changes --
M
Totally makes sense for a user, which is why we don't do it. /some sarcasm
Yeah this is part of the jclouds idioms. The domain objects are mostly data
access objects, so they really don't have functionality outside of some
serialization information.
All the call information is under
15 matches
Mail list logo
