Community
Participate
Working Groups
EMF 2.6M4 changes the EModelElement inheritance and adds eInvoke. This doesn't yet break MDT/OCL directly; just usage of eXXX mothods in OCL expressions. However when Kenn adds the code to exploit eInvoke, we will be broken, so we might as well change the dependency to [2.6.0 3.0.0) now everywhere (except emf.ocl.examples*).
Created attachment 157874 [details] Dependency changes Attached changes EMF dependency in o.e.o to 2.6 and then propagates it through other plugins rather than respecifying it. Attached also changes the Platform core dependency to 3.2 throughout, rather than a hotch-potch of creation dates. I doubt we work on 3.2 but let EMF impose the lower bound.
The patch is sensible and looks harmless. My +1.
I'm not sure if changing the dependency of a generated plugin such us o.e.o.edit is advisable and/or necessary, and I don't see any problem iwhich depedens on different versions of the same. In any case.... who cares.... As you comment, EMF will impose real the minimum version of the needed Platform's core .... Go ahead. Cheers, Adolfo.
Sorry, when I said > and I don't see any problem iwhich depedens on different versions of the same. I meant: I don't see any problem if we have different plugins which require different versions of the same Platform core plugin. Cheers, Adolfo.
Committed to HEAD.
Closing