[
https://issues.apache.org/jira/browse/DTACLOUD-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ronelle Landy closed DTACLOUD-507.
----------------------------------
Resolution: Fixed
Tested with https://github.com/wingedmonkey/wingedmonkey/pull/280
deltacloud-core01.1.3 pre-release (gem cut for testing only) and
https://github.com/deltacloud/core/pull/5.
Was able to start wingedmonkey with a combination of those pull request and
gems.
Closing this JIRA out as the related pull request has been closed.
> Possible conflict of Deltacloud model classes with Rails classes
> ----------------------------------------------------------------
>
> Key: DTACLOUD-507
> URL: https://issues.apache.org/jira/browse/DTACLOUD-507
> Project: DeltaCloud
> Issue Type: Bug
> Reporter: Michal Fojtik
> Assignee: Michal Fojtik
> Priority: Blocker
>
> Right now the models we have in Deltacloud does not have any namespece.
> Models like 'Provider' or 'Image' exists in the 'global' namespace.
> This could be a problem when you have an Rails app that define models with
> same name (Provider for example).
> I think this is a good argument to make *all* Deltacloud models live in the
> Deltacloud namespace (Deltacloud::Provider).
--
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
