[
https://issues.apache.org/jira/browse/JCLOUDS-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532588#comment-14532588
]
ASF subversion and git services commented on JCLOUDS-901:
---------------------------------------------------------
Commit 2c53ef38a5caf5621fcf74983636fbd00341a674 in jclouds's branch
refs/heads/master from [~karel.verva...@telenet.be]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=2c53ef3 ]
JCLOUDS-901 Moved CloudStack javadocs around
During the rename from *Client to *Api the javadocs were shuffled
around. This commit moves them back to the correct methods.
> Wrong javadocs in cloudstack VolumeApi
> --------------------------------------
>
> Key: JCLOUDS-901
> URL: https://issues.apache.org/jira/browse/JCLOUDS-901
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 1.7.3, 2.0.0, 1.8.2, 1.9.1
> Reporter: Karel Vervaeke
> Priority: Minor
>
> While looking into JCLOUDS-593 I noticed some weirdness in the javadocs.
> None of their javadoc methods make sense:
> - docs for createVolumeByDiskOfferingInZone say it's by snapshotId
> - docs for createVolumeByCustomDOIZ say it's for listing volumes
> - docs for attachVolume say it's for deleting attached volumes (does that
> even work?)
> - docs for detachVolume say it's for attaching volumes
> etcetera.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
