Eclipse Community Forums - RDF feed
https://www.eclipse.org/forums/
Eclipse Community ForumsProblem with merging multiplicity-many eOpposites
https://www.eclipse.org/forums/index.php/mv/msg/1082874/1749158/#msg_1749158
I am trying to resolve a merge conflict involving a multiplicity-many eOpposite reference. I would expect this to work out-of-the-box, since it seems that this case is implemented by the default equivalence engine (DefaultEquiEngine). However, the merge does not seem to work as expected.
Here are some details.
I have two classes (A and B), referring to each other by references A.b(1) and B.a(*). These references are eOpposites and non-containment. I then create a conflicting change on A.b. After resolving the conflict on A.b, I can see that the B.a reference is not updated.
Is this a known limitation of the DefaultEquiEngine? If so, do you have any suggestions for overcoming it?
Thanks in advance!
Vlad
]]>Vlad Acretoaie2016-12-02T12:47:20-00:00Re: Problem with merging multiplicity-many eOpposites
https://www.eclipse.org/forums/index.php/mv/msg/1082874/1749165/#msg_1749165
After investigating a bit more, I think the root cause of my problem goes a little further. I am executing model merging twice, and it seems that the second time there is some information missing.
I will very likely open a new forum thread for this, but as of now it looks like the DefaultEquiEngine actually works as it should.
If possible, this thread should be deleted.
Cheers,
Vlad]]>Vlad Acretoaie2016-12-02T14:18:54-00:00Re: Problem with merging multiplicity-many eOpposites
https://www.eclipse.org/forums/index.php/mv/msg/1082874/1749299/#msg_1749299
We can't delete threads, but thanks for the heads up.