Community
Participate
Working Groups
Let's consider two models A and B, both referring to C. I have one instance of A and C in the same folder I have one instance of B in another folder The reference to C is relative to the same folder in both cases. Now it seems the diff engine consider that A and B are different, since the reference in B is not resolved. In fact A and B are similar, so I would think there should be no diff there. The fact that the reference is broken is something independent from the model content. Something worse is that if I copy C in the folder where B is, I still get a diff on the C reference.
Resolving inter-models references is planned for 1.0 ( http://wiki.eclipse.org/index.php/EMF_Compare#Roadmap )
Hi, Bug #244000 has been partly fix and inter-model references will not be accurately detected as differences when they truly changed, and won't display any change when not. As stated on bug #244000, comment #3 , this will work with local comparison and not yet with VCS.
Proxy resolution capabilities have been added to EMF Compare and will be available in the next build. We'll also be building a second feature "EMF Compare Subversive Integration" as subversive does not make use of the Team API as CVS does. Behavior of other VCS haven't been confirmed yet. With these, cross-model references are now properly resolved to the accurate version according to the currently compared model revision.
Correction available in 0.9.0M5
Closing our "resolved" and "verified" bugs.
