Eclipse Community Forums: Compare » [EMF Compare] Exchange ScopeProvider in UI plugin

Help

Home

Home » Modeling » Compare » [EMF Compare] Exchange ScopeProvider in UI plugin

Show: Today's Messages :: Show Polls :: Message Navigator

[EMF Compare] Exchange ScopeProvider in UI plugin [message #1060789]

Tue, 28 May 2013 12:41

Simon Schwichtenberg

Messages: 127
Registered: September 2011

Senior Member

Hi,

I am implementing a customized MatchEngine for uml models that bases on EMF compare 1.3. The engine should ignore Packages, but should compare all Classes within all Packages. In the models I want to compare there are no nested Packages. So the engine should compare the models as if all Classes would be on the root level.

After reading the dev doc, I came up with the idea to override the scopeprovider, but I can't see how I could exchange it without copying nearly all of the code from the GenericMatchEngine.

My idea is to set the MatchOptions.OPTION_MATCH_SCOPE_PROVIDER in the optionsMap, but I cannot override the private field org.eclipse.emf.compare.match.engine.GenericMatchEngine.structuredOptions. Even the updateSetting()-method cannot be used.

What is the intended way to exchange the scopeprovider?

Report message to a moderator

Re: [EMF Compare] Exchange ScopeProvider in UI plugin [message #1060843 is a reply to message #1060789]

Tue, 28 May 2013 15:36

Simon Schwichtenberg

Messages: 127
Registered: September 2011

Senior Member

I guess I can't use the scopeprovider anyway, because when the package is not in the scope, the contents are also not in the scope.

Report message to a moderator

Re: [EMF Compare] Exchange ScopeProvider in UI plugin [message #1060921 is a reply to message #1060843]

Wed, 29 May 2013 07:31

Laurent Goubet

Messages: 1895
Registered: July 2009

Senior Member

Hi,

You are hitting one of the limitations of EMF Compare 1 head-on. You have to keep the packages within the scope for their content to be matched. However, you might be able to set your engine up to ignore all references of your package, effectively ignoring all differences on it. You can do so by overriding the GenericDiffEngine and providing your own attribute/reference checker from the appropriate getter.

If you can switch to EMF Compare 2, the scoping mechanism allows you to easily change what EObjects should be considered for comparison, without restriction.

Laurent Goubet
Obeo

Report message to a moderator

Previous Topic:	org.eclipse.emf.compare singleton bundle?
Next Topic:	UnmatchElement List vs total

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Sep 17 19:04:35 GMT 2021

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter