Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337591 - Enable ModelComparator to supply own options to match engine
Summary: Enable ModelComparator to supply own options to match engine
Status: CLOSED WONTFIX
Alias: None
Product: EMFCompare
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: EMF Compare CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-18 12:05 EST by Tilman Wilhelm CLA
Modified: 2013-01-11 10:55 EST (History)
1 user (show)

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 Tilman Wilhelm CLA 2011-02-18 12:05:08 EST 
Build Identifier: 201009150438

When using ModelComparator.compare() it is not possible to supply own settings that are then given to the match engine option map. For our concerns it would be nice if the match engine could have access to the CompareSettings for instance.
Building a workaround and not calling ModelComparator.compare(), but still using the resource handling of ModelComparator, works, but it's a lot re-implementing stuff that is already done there. So it would be nice if you could somehow add this functionality to the ModelComparator class.
Another small improvement concerns the Match Mode Dialog, it would be nice if one could not show that dialog but provide that option via the method call.

Reproducible: Always
Comment 1 Laurent Goubet CLA 2013-01-11 10:55:46 EST 
Will not be fixed on the 1.* stream.

EMF Compare 2 should (already) be better in terms of customization and API.