Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Errors in infrastructure.occie #26

Closed
philippemerle opened this issue Nov 11, 2015 · 1 comment
Closed

Errors in infrastructure.occie #26

philippemerle opened this issue Nov 11, 2015 · 1 comment
Assignees
@philippemerle
Labels
bug

Comments

@philippemerle
Copy link
Member

File .....infrastructure/model/ infrastructure.occie contains several errors:

  • the type of the attribute "occi.network.state" of the network kind must be NetworkStatus instead of ComputeStatus
  • the default of some attributes must not be defined instead of setting with an empty string.
@philippemerle philippemerle self-assigned this Nov 11, 2015
philippemerle added a commit that referenced this issue Nov 12, 2015
@philippemerle
Updated according issue #26
b4541df
@philippemerle
Copy link
Member Author

It is needed to:

  1. regenerate model/infrastructure.ecore
  2. then execute genmodel to regenerate EMF specific Java code.

@wpiers wpiers assigned wpiers and unassigned philippemerle Dec 4, 2015
philippemerle added a commit that referenced this issue Mar 15, 2016
@philippemerle
Regenerated Infrastructure.ecore and run genmodel.
8e933c2 
Related to issue #26.
philippemerle added a commit that referenced this issue Mar 15, 2016
@philippemerle
Used NetworkStatus instead of ComputeStatus.
89a64e9 
Related to issue #26
philippemerle added a commit that referenced this issue Mar 29, 2016
@philippemerle
Related #26
b7710d6 
regenerate Ecore metamodel and Java model/edit code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@philippemerle philippemerle

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@philippemerle @wpiers