Community
Participate
Working Groups
M7. A compare against CVS after adding one line (a new derived class) to /org.eclipse.ocl.examples.xtext.oclinecore/model/OCLinEcoreCST.ecore 1.3 reports 25 errors. The model has the following reference: ../../org.eclipse.ocl.examples.xtext.base/model/BaseCST.ecore#//PackageCS requiring that the CVS model be resolved against another (possibly CVS) model. In this scenario EMF compare reports 25 changes, the spurious changes all being due to the apparent use of null for the unresolved CVS elements. Presumably EMF compare should leave external proxies unresolved so that they can be compared without activating 'deep' issues.
The match, diff and merge process have seen a great deal of improvement in the past week, with the addition of unit tests for most of the different use cases (one use case = one possible "diff" between models) we could think of. The particular issue of proxy resolution is one of the things that has been tested and fixed. Could your verify whether you still reproduce with the latest integration builds? These changes have been pushed on both master and the 1.2 maintenance stream. They are available in the builds - 1.2 integration : I201108090404 - 1.3 integration : I201108090415
Closing this as worksforme since these issues should have been fixed last year.
Surely this is resolved FIXED since the problem was genuine and went away as a result of ongoing progress.
Ed, I set this as "worksforme" since I never actually reproduce these issues before fixing them :). I can change the resolution if you'd rather, that's just a flag on bugzilla after all ^^.
