Bug 510392 - Let clients register FeatureFilters to be used in DefaultDiffEngine depending on a comparison context
Summary: Let clients register FeatureFilters to be used in DefaultDiffEngine depending...
Status: NEW
Alias: None
Product: EMFCompare
Classification: Modeling
Component: Core (show other bugs)
Version: 3.3.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: EMF Compare CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-12 14:38 EST by Philip Langer CLA
Modified: 2017-01-12 14:38 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Langer CLA 2017-01-12 14:38:13 EST 
Currently, feature filters [1] can only be added to custom diff engines. However, it would be useful to be able to register feature filters for a specific comparison context so that those custom feature filters are considered by the DefaultDiffEngine when the specific comparison context applies.

We suffered this lack of such a mechanism when addressing bug 508665, where we would have liked to ignore a specific feature for UML models. However, we don't want to introduce a UML-specific diff engine, because users would then have to switch between different engines depending on the model they compare, which is not satisfactory.

Once we have such a mechanism, we should revert the fix of bug 508665 and register a feature filter for such diffs instead.

[1] https://www.eclipse.org/emf/compare/documentation/latest/developer/developer-guide.html#Changing_the_FeatureFilter