Closed eclipse-ocl-bot closed 1 month ago
By Adolfo Sanchez-Barbudo Herrera on Sep 17, 2009 12:19
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.
By Ed Willink on Sep 17, 2009 13:03
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.
By Ed Willink on Mar 07, 2010 16:26
Created attachment 161244 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).
:compression: OCLInEcoreEditor.zip
By Ed Willink on Mar 11, 2010 10:40
For better or worse, the editor and associated plugins are now in CVS HEAD under example/...
It should be possible to upgrade an existing:
By Ed Willink on Mar 11, 2010 10:47
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.
By Alexander Igdalov on May 27, 2010 15:25
Marking as CLOSED FIXED for Helios since MDT OCL has editor support in examples, though not IMP-based.
By Ed Willink on May 27, 2011 02:54
Closing
| --- | --- | | Bugzilla Link | 289761 | | Status | CLOSED FIXED | | Importance | P3 normal | | Reported | Sep 17, 2009 11:40 EDT | | Modified | May 27, 2011 02:54 EDT | | Version | 1.3.0 | | Reporter | Ed Willink |
Description
This thread started to avoid initial discussion on the desirability of this\ migration clouding discussion of feature/plug-in reorganisation.
This thread continues where the mdt-ocl-dev: "MDT-OCL project organisation for add-ons (editor etc)" thread left off.\
It was agreed that in mprinciple it would be good to provide an OCL editor for Helios, and that the M2M/QVT Declarative OCL Editor was a promising candidate that unfortunately had undesirable incubation dependencies on IMP, LPG2 and SHRIKE.
I undertook to investigate replacing the IMP usage by direct SWT usage. This proved to be far from easy since IMP was offering many fairly minor facilities.
The LPG2 dependency is being addressed by Adolfo so that we expect LPG2 to be in Orbit shortly.
The IMP dependencies have simplified so that the org.eclipse.imp.runtime plugin no longer has any other dependencies not satisfied by the Galileo Modeling Package.
I therefore created a copy of IMP runtime so that M2M/QVT Declarative could redistribute an IMP runtime with patches. This avoids dependencies on IMP which has no plan to align with Helios milestones.
I therefore recommend migration of the M2M/QVT Declarative OCL Editor to\ MDT/OCL.
I will post code if the team is happy with this proposal.