deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michal Fojtik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DTACLOUD-507) Possible conflict of Deltacloud model classes with Rails classes
Date Thu, 07 Mar 2013 13:14:12 GMT

    [ https://issues.apache.org/jira/browse/DTACLOUD-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595865#comment-13595865
] 

Michal Fojtik commented on DTACLOUD-507:
----------------------------------------

Fix available here: http://tracker.deltacloud.org/set/372
                
> 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
>
> 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

Mime
View raw message