Move OCL out of .ecore into separate .oclinecore file
Issue #17
resolved
Having the OCL concrete syntax directly in the .ecore file is apparently a bad idea.
I see only one problem with the attached; you have stored OCLinEcore concrete syntax as a .ecore file, so opening the file with any EMF tool bombs. Use .oclinecore for OCLinEcore concrete syntax.
Move it to separate file. If I am not mistaken this also allows for formatting and comments.
Comments (5)
-
reporter
-
reporter
- changed component to Metamodel
-
reporter
- removed responsible
-
reporter
- changed status to resolved
Resolved with new validator project. Except that the default EMF validation (e.g., in the generated editor) will not evaluate the .ocl file(s) of the validator project.
-
reporter
-
assigned issue to
Laura Martellotto
-
assigned issue to
- Log in to comment
This might not be feasible, because OCL in a separate file won't be executed automatically. At least not currently. An option would be to modify the generated
RamValidatorinca.mcgill.cs.sel.ram.util.