|Re: EMF Compare of combined models, comparing packages at new different levels [message #957483 is a reply to message #956836]
||Thu, 25 October 2012 08:56
|| Laurent Goubet
Registered: July 2009
First things first, which version of EMF Compare are you using?
EMF Compare 2.0 (and 1.3.1) will both load the whole logical model when comparing. This means that when you try and compare "mypackage.ecore" with another model, EMF Compare will load "mypackage.ecore" and all of the other resources it reference, in this case "mysubpacakage1.ecore" and "mysubpacakage2.ecore". In short, if you simply compare your two versions of "mypackage.ecore", EMF Compare should just work. Note that this assumes that "mypackage" does indeed reference the two sub-packages (i.e. when you load "mypackage" in an ecore editor and right-click > validate it, you have the two other resources loaded in that editor : they are "fragments" of mypackage).
2.0 will see (at least) two differences that correspond to the "unfragmenting" of your model (i.e. the move of subpackage1 and subpackage2 into mypackage). Version 1.* had a limitation that prevented us from detecting that.
[edit : you might be interested in my rant about the Logical models in EMF Compare 2...]
[Updated on: Thu, 25 October 2012 08:57]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.02230 seconds