Closed eclipse-ocl-bot closed 1 month ago
By Ed Willink on Jun 03, 2015 12:59
(In reply to Ed Willink from comment #0)
The non extension point org.eclipse.ocl.pivot.uml facilities should be initialized in org.eclipse.ocl.pivot.uml.PivotUMLPlugin.start().
There should be a JUnit test demonstrating UML validation as seen by the user in the UML Model Editor.
Pushed to master for RC4.
JUnit test starts the UML Model Editor and uses it to load the models, but it is not obvious how to observe the Validation Dialog response and so the subsequent validation is independent.
| --- | --- | | Bugzilla Link | 469251 | | Status | RESOLVED FIXED | | Importance | P3 normal | | Reported | Jun 03, 2015 06:32 EDT | | Modified | Jun 03, 2015 12:59 EDT | | Blocks | 469232 | | Reporter | Ed Willink |
Description
From Bug 469232.
Open E:\GIT\org.eclipse.papyrus\tests\recipes\plugins\uml\org.eclipse.papyrus.uml.ocl.recipetest\models\validation\model.di and validate model.
Gives:
[ModalContext] WARN org.eclipse.ocl.pivot.uml.UMLStandaloneSetup - UMLStandaloneSetup.init() should be called before using OCL's UML facilities
Same problem for the model.uml
The non extension point org.eclipse.ocl.pivot.uml facilities should be initialized in org.eclipse.ocl.pivot.uml.PivotUMLPlugin.start().
There should be a JUnit test demonstrating UML validation as seen by the user in the UML Model Editor.