|
Re: EMF Compare fails [message #138609 is a reply to message #138531] |
Wed, 15 July 2009 08:10 |
|
This is a multi-part message in MIME format.
--------------060502000508020604010806
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Hi Usul,
Judging by the fact you're calling the comparison from unit tests and
the failure appears right off the bat, my best guess is that you're
calling MatchService.doMatch() on models that are not contained within
Resources. You can either
1) call MatchService.doContentMatch() instead (that would see all
inter-model differences as "Add" or "Remove" operations)
or
2) create Resources to contain your models and possibly create a
ResourceSet to contain these Resources and then call
MatchService.doMatch() on it.
Laurent Goubet
Obeo
Usul a
|
|
|
|
Re: EMF Compare fails [message #621133 is a reply to message #138531] |
Wed, 15 July 2009 08:10 |
|
This is a multi-part message in MIME format.
--------------060502000508020604010806
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Hi Usul,
Judging by the fact you're calling the comparison from unit tests and
the failure appears right off the bat, my best guess is that you're
calling MatchService.doMatch() on models that are not contained within
Resources. You can either
1) call MatchService.doContentMatch() instead (that would see all
inter-model differences as "Add" or "Remove" operations)
or
2) create Resources to contain your models and possibly create a
ResourceSet to contain these Resources and then call
MatchService.doMatch() on it.
Laurent Goubet
Obeo
Usul a
|
|
|
|
Powered by
FUDForum. Page generated in 0.47667 seconds