Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 370727 - It is not possible to call the ModelComparator.compare() API inside an existing thread UI
Summary: It is not possible to call the ModelComparator.compare() API inside an existi...
Status: CLOSED FIXED
Alias: None
Product: EMFCompare
Classification: Modeling
Component: Core (show other bugs)
Version: 1.3   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: EMF Compare CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-06 09:46 EST by Cedric Notot CLA
Modified: 2012-02-28 10:17 EST (History)
1 user (show)

See Also:

Attachments
Patch (12.31 KB, patch)
2012-02-06 09:46 EST, Cedric Notot CLA 		laurent.goubet: iplog+
Details | Diff
View All 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 Cedric Notot CLA 2012-02-06 09:46:05 EST 
Created attachment 210587 [details]
Patch

It is not possible to call the ModelComparator.compare() API inside an existing thread UI.

I have attached a patch where I added a method: compareSilentlyInThreadUI() to do that. Moreover, this one allows not to get the dialog to select a resource set comparison or resource only. Calling this, it launches a resource set comparison.
Comment 1 Laurent Goubet CLA 2012-02-28 10:17:18 EST 
This patch has been commited on master and the fix will be available in 1.3