Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 298279 - [releng] Raise EMF dependency to 2.6
Summary: [releng] Raise EMF dependency to 2.6
Status: CLOSED FIXED
Alias: None
Product: OCL
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: OCL Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 290103
  Show dependency tree
 
Reported: 2009-12-21 03:26 EST by Ed Willink CLA
Modified: 2013-05-22 14:15 EDT (History)
1 user (show)

See Also:


Attachments
Dependency changes (7.50 KB, patch)
2010-02-02 02:35 EST, Ed Willink CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2009-12-21 03:26:41 EST
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*).
Comment 1 Ed Willink CLA 2010-02-02 02:35:45 EST
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.
Comment 2 Alexander Igdalov CLA 2010-02-03 05:41:49 EST
The patch is sensible and looks harmless. My +1.
Comment 3 Adolfo Sanchez-Barbudo Herrera CLA 2010-02-03 05:43:49 EST
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.
Comment 4 Adolfo Sanchez-Barbudo Herrera CLA 2010-02-03 05:47:17 EST
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.
Comment 5 Ed Willink CLA 2010-02-03 15:03:18 EST
Committed to HEAD.
Comment 6 Ed Willink CLA 2011-05-27 02:55:08 EDT
Closing