[
https://issues.apache.org/jira/browse/JCLOUDS-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768147#comment-13768147
]
ASF subversion and git services commented on JCLOUDS-277:
---------------------------------------------------------
Commit 1fc5806ec9fdae248b9e7de5267d52eb8b09d193 in branch refs/heads/master
from [~joshvote]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;h=1fc5806 ]
JCLOUDS-277: Made the description in org.jclouds.compute.domain.Image nullable
> Make compute image descriptions nullable
> ----------------------------------------
>
> Key: JCLOUDS-277
> URL: https://issues.apache.org/jira/browse/JCLOUDS-277
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 1.7.0
> Reporter: Joshua Vote
> Assignee: Joshua Vote
> Fix For: 1.7.0
>
> Attachments: JCLOUDS-277.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> org.jclouds.compute.domain.Image has "name" and "description" properties.
> "name" is Nullable but "description" isn't. This seems to be a little
> inconsistent, why should an Image description String be so strict about its
> contents if the name is completely ambivalent?
> While this seems to be a pretty trivial matter the "openstack-nova" provider
> has no concept of an Image description, only a name. This is worked around by
> assigning the "openstack-nova" name to both the JClouds Image name and
> description. I'm experiencing an issue when the "openstack-nova" has a null
> name and tries to assign it to the currently NOT nullable description.
> I hope this makes sense :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
