| Summary: | EMF Compare should resolve cross-model references | ||
|---|---|---|---|
| Product: | [Modeling] EMFCompare | Reporter: | Laurent Goubet <laurent.goubet> |
| Component: | Core | Assignee: | EMF Compare <emf.compare-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | cedric.brun, ed, hjoensson, sbouchet |
| Version: | 1.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 199877 | ||
| Bug Blocks: | 229663 | ||
|
Description
Laurent Goubet
A few user selectable options are needed. For instance: When comparing a multi-package multi-Ecore file model, I would like a deep compare so that the equivalent classes in all 'left' model files are recognised to be the 'same' as the 'right' model files. When comparing a multi-package multi-Ecore file model with an equivalent multi-package single-Ecore file model, I would like the deep compare to ignore file partitioning. When double clicking an Ecore model in the CVS synchronisation browser, or just comparing with HEAD, I would like the comparison to be shallow so that the spelling rather than the value of proxies is compared. Options such as 'same' by hierarchical name, ID attribute, xmi:id, ... should be selectable from a right button menu, in the same way as 'ignore whitespace' in the satndard compare editor. *** Bug 256582 has been marked as a duplicate of this bug. *** A first implementation of a "resource set wide differencing" has been commited on HEAD. The next build will contain this modification and allow for the accurate detection of changes on inter-model references. This will work fine with local comparison, though proxy resolving is planned for bug #199877 thus comparison with VCS will not detect these references and fall back on the previous behavior. 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. FIX available in 0.9.0M5 Closing our "resolved" and "verified" bugs. |