Eclipse Community Forums: Compare » Invalid Comparison result with orphan fields on both sides

Home » Modeling » Compare » Invalid Comparison result with orphan fields on both sides(Invalid Comparison result with orphan fields on both sides)

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

Invalid Comparison result with orphan fields on both sides [message #1018672]

Thu, 14 March 2013 09:39

Pradeep Badiger

Messages: 53
Registered: November 2012

Member

Hi,

I am doing a comparison of two model ecore files. Both the ecore files have few common fields and few orphan fields. When i do a comparison, the ophan fields gets matched based on their order and doesnt show that fields are added/removed. Rather it shows the field attributes are modified. Please check the attachement.

Is this correct? How do we compare the content when we have orphans on both the sides.

thanks,
Pradeep V.B.

Attachment: OrphanFieldsOnBothSides.jpg
(Size: 155.69KB, Downloaded 341 times)

Report message to a moderator

Re: Invalid Comparison result with orphan fields on both sides [message #1020494 is a reply to message #1018672]

Mon, 18 March 2013 10:04

Laurent Goubet

Messages: 1902
Registered: July 2009

Senior Member

Hi,

EMF Compare uses a "distance" algorithm in order to match your models together since they do not have identifiers. In this case, only the name and location differs between your two models, and this given a distance between the two that is below the threshold at which we assume the two are different.

There's been a lot of improvements within this proximity matching algorithm in the last few months as we work towards the 2.1.0 release. It seems like your using EMF Compare 1.3.0, you might want to give a chance to one of the milestone builds of 2.1, which should give similar to better results. You can retrieve the M5 build from the following p2 update site (use "Help > Install new software..." and paste in this URL to use that update site):

http://download.eclipse.org/modeling/emf/compare/updates/milestones/2.1

Note that EMF Compare 2.1.0 M6 will be available for download tomorrow, it also features some new improvements (notably on the performance side) for your use case. You can download the latest nightly (which should be quite close to the final M6 state) from the following update site (bear in mind that this is a nightly using what the team is currently working on):

https://hudson.eclipse.org/hudson/view/Modeling/job/emf-compare-master/lastSuccessfulBuild/artifact/packaging/org.eclipse.emf.compare.update/target/repository/

Laurent Goubet
Obeo

Report message to a moderator

Re: Invalid Comparison result with orphan fields on both sides [message #1020883 is a reply to message #1020494]

Tue, 19 March 2013 05:28

Pradeep Badiger

Messages: 53
Registered: November 2012

Member

Hi Laurent,

Thanks for the update.

I have been trying to compare two ecore model files programmatically using MatchService and DiffService. Are these classes removed in 2.1? Do we have any equivalent utility classes for comparison?

thanks,
Pradeep V.B.

Report message to a moderator

Re: Invalid Comparison result with orphan fields on both sides [message #1020946 is a reply to message #1020883]

Tue, 19 March 2013 08:36

Laurent Goubet

Messages: 1902
Registered: July 2009

Senior Member

Hi,

The core concepts of EMF Compare evolved completely, though we hope that was for the best. You might want to look at the FAQ to see how to compare programatically with EMF Compare 2. We do not have a migration guide to ease this transition, but do not hesitate to ask if you cannot find what you need in the code base.

Laurent Goubet
Obeo

Report message to a moderator