[
https://issues.apache.org/jira/browse/DTACLOUD-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627650#comment-13627650
]
Michal Fojtik commented on DTACLOUD-507:
----------------------------------------
Please note there is also change to '#require!' method above. This is important
if you want to use latest Deltacloud bits or version 1.1.2.
This initializer with work with this[1] version of DC. NOTE: This is
pre-release version, but include fixes that makes it able to be mounted into
Rack again :)
If you want to use 1.1.2 (not the gem below), instead of :mock_initialize =>
true, you need to add this line before 'require!':
require 'initializers/mock_initialize'
[1] http://omicron.mifo.sk/deltacloud-core-1.1.3.gem
> 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
