Eclipse Community Forums: EMF » [EMF Compare] Merging non-containment references

Home » Modeling » EMF » [EMF Compare] Merging non-containment references

[EMF Compare] Merging non-containment references [message #500370]

Wed, 25 November 2009 14:05

Eclipse User

Originally posted by: mail.andreasscharf.com

Hi,

I have a question concerning merging non-containment references. I have
two ecore models:

ModelA
- EClassA
- EClassB

ModelB
- EClassA
- EClassB
- someReference : EClassA

If I now compare ModelA against ModelB the deleted reference is
recognized. I then merge the change from right to left and what I
was expecting is that I now have 'someReference:EClassA' under EClass B
which is basically is true. But the type of 'someReference' is a cross
reference into ModelB rather than to (the matched) EClassA in ModelA.

Is that wanted behavior?

Kind regards,
Andreas

Re: [EMF Compare] Merging non-containment references [message #500466 is a reply to message #500370]

Thu, 26 November 2009 04:46

Eclipse User

This is a multi-part message in MIME format.
--------------080402080706030806080105
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Hi Andreas,

Nope, that would be a bug. Stephen McCants raised a number of issues
through the JUnit tests attached to bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=294336 yet I haven't
managed to fully fix them and integrate these tests yet. Does your bug
fall in one of these categories? If not, please raise a new one for your
particular issue.

Laurent Goubet
Obeo

Andreas Scharf wrote:
> Hi,
>
> I have a question concerning merging non-containment references. I have
> two ecore models:
>
> ModelA
> - EClassA
> - EClassB
>
>
> ModelB
> - EClassA
> - EClassB
> - someReference : EClassA
>
> If I now compare ModelA against ModelB the deleted reference is
> recognized. I then merge the change from right to left and what I
> was expecting is that I now have 'someReference:EClassA' under EClass B
> which is basically is true. But the type of 'someReference' is a cross
> reference into ModelB rather than to (the matched) EClassA in ModelA.
>
> Is that wanted behavior?
>
> Kind regards,
> Andreas

--------------080402080706030806080105
Content-Type: text/x-vcard; charset=utf-8;
name="laurent_goubet.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="laurent_goubet.vcf"

begin:vcard
fn:Laurent Goubet
n:Goubet;Laurent
org:<a href="http://www.obeo.fr">Obeo</a>
email;internet:laurent.goubet@obeo.fr
url:http://www.obeo.fr
version:2.1
end:vcard

--------------080402080706030806080105--

Previous Topic:	the EMF Model interfaces can not be resolved.
Next Topic:	EObject to XML

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 24 18:24:10 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter