Problem with merging multiplicity-many eOpposites [message #1749158] |
Fri, 02 December 2016 07:47  |
Eclipse User |
|
|
|
Hi,
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
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.12149 seconds