| Summary: | [editor] Migrate the M2M/QVT Declarative OCL Editor to MDT/OCL | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] OCL | Reporter: | Ed Willink <ed> | ||||
| Component: | Core | Assignee: | OCL Inbox <mdt-ocl-inbox> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | adolfosbh, alexander.igdalov | ||||
| Version: | 1.3.0 | Keywords: | plan | ||||
| Target Milestone: | 3.0.0 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | Usability | ||||||
| Attachments: |
|
||||||
|
Description
Ed Willink
So, the solution is copying the IMP runtime... I don't like too much the idea, but I guess that there is not any alternative... I'll +1, but take into account that the LPG v2.0.18 should be copied when it comes up (I've just checked that it's not in sourceforge yet). Another consideration could be addressing this bug in the experimental branch, so that it could be merged altoguether when LPG v2.0.18 appears (merging new plugins/packages should be trivial). Cheers, Adolfo. I don't like copying the runtime either, but it seems the least bad solution. At the moment you're only +1'ing the principle of the editor migration. It certainly won't be committed before a further round of +1's in this bug and not before LPG2.0.18 is in Orbit. If LPG2.0.18 does take a long time, then yes the experimental branch wiould be appropriate. Created attachment 161244 [details]
Work in progress OCL in Ecore Editor
Attached is not yet ready for review, but may be of interest since it provides an OCL Document editor and an OCL in Ecore editor.
Prerequisites:
IMP Runtime 0.1.103 from IMP's SVN.
LPG 2.0.17 from Orbit
lpg.runtime from LPG's CVS (or correct IMP Runtime's dependency to lpg.runtime.java).
For better or worse, the editor and associated plugins are now in CVS HEAD under example/... It should be possible to upgrade an existing: Continuing: It should be possible to upgrade an existing: Platform + EMF + UML2 + OCL + Subclipse installation by using Import Project Set ... from org.eclipse.ocl/releng/psfs/examples.psf examples.psf has a comment on getting Subclipse. The PSF fetches the EMF Transaction and EMF Validation dependencies and IMP Runtime. The lpg.runtime name confusion doesn't seem to matter when using project resources. New->Project... Examples ... OCL offers the RoyalAndLoyal example. --- Just need to beat out the bugs now and wait for IMP Runtime 0.1.104 on the Update Site. Marking as CLOSED FIXED for Helios since MDT OCL has editor support in examples, though not IMP-based. Closing |