[m2t-dev] Xpand build against EMF 2.6 cancelled

[Achim Demelt <a.demelt@xxxxxxxxxxxxx>]

Hi all,

As discussed in yesterday's telco, I investigated into building parts of Xpand 
against EMF 2.6 and the Eclipse Platform 3.6 in order to allow _some_ new 
Xtend features to use EMF 2.6.

It seems that this would actually require to set up a completely separate 
build, because Athena can work only work with exactly one platform and one set 
of dependencyURLs. The original Xpand build would remain unchanged (against 
Platform 3.5 and EMF 2.5). In addition to that we would have to have another 
releng build that uses the 3.6 Platform and EMF 2.6 and build just the new 
plugin(s) and fragment(s). Both builds would produce individual update sites. 
The final Xpand site would have to be an aggregate repository, combining the 
two individual sites.

I chatted with Sven and we both think that this is kind of overkill. We 
discussed that calling EOperations from Xtend 
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=297515) can probably be done 
using Java reflection. If EObject.eInvoke() exists, we're running with EMF 2.6 
and we can use it. If not, well, then not.

The other enhancement I proposed is probably pretty far off from the 
mainstream, so we're not hurting ourselves if we don't provide this feature at 
this point in time. I opened this bug 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=299539 and attached the 
implementation and test cases for early adopters to try out.

This means, we'll cancel building any parts of Xpand against EMF 2.6. 
Objections?

Cheers,
 Achim