Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 260647 - Separate ImperativeOCL meta-model from QVTO
Summary: Separate ImperativeOCL meta-model from QVTO
Status: RESOLVED FIXED
Alias: None
Product: QVTo
Classification: Modeling
Component: Engine (show other bugs)
Version: 1.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 2.0 M5   Edit
Assignee: Radomil Dvorak CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-11 18:17 EST by Radomil Dvorak CLA
Modified: 2009-01-13 11:55 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Radomil Dvorak CLA 2009-01-11 18:17:28 EST 
1) Cleanup remaining differences from the OMG compliant model
  - still refers to classes from generic OCL metamodel but should refer to OCL ecore bindings instead
    (for example OCLEXpression<EClassifer>, Variable<...>)
 - fix structural differences in WhileExp, VariableInitExp
 
2) add dependency to 'org.eclipse.m2m.qvt.oml.ecore.imperativeocl' hosting the final meta-model.
Comment 1 Radomil Dvorak CLA 2009-01-13 11:55:15 EST 
Committed.

This SCR introduced physical split into a separate interim ImperativeOCL located in /org.eclipse.m2m.qvt.oml/model/Imperative and
structurally identical to OMG provided metamodel.

The next step (in a separate SCR) will be add dependency to /org.eclipse.m2m.qvt.oml.ecore.imperativeocl/model and
remove the interm model as soon as 'org.eclipse.m2m.qvt.oml.ecore.imperativeocl' plugin gets handled by releng.