search

eclipse-uml2 / uml2

An EMF-based implementation of the UML 2.x metamodel for the Eclipse platform.
Eclipse Public License 2.0
5 stars 4 forks source link

Package merge does not handle matched association ends with different navigability correctly #44

Open eclipse-uml2-bot opened 7 hours ago

eclipse-uml2-bot commented 7 hours ago

| --- | --- | | Bugzilla Link | 292302 | | Status | NEW | | Importance | P3 normal | | Reported | Oct 14, 2009 14:13 EDT | | Modified | Feb 10, 2014 21:11 EDT | | Reporter | Maged Elaasar |

Description

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/3.0.195.25 Safari/532.0\ Build Identifier: 20090920-1017

Package merge algorithm does not merge association ends that are navigable in one association and non-navigable in another to-be-merged-with association. Instead, it puts them both in the merged model and the merged association's memberEnd gets 3 refs to ends.

Reproducible: Always

Steps to Reproduce:\ Create package P1 with:\ Class X\ Class Y\ Association A (bidirectional from X to Y with roles X::y and Y::x)

Create package P2 with:\ Class X\ Class Y\ Association A (unidirectional from X and Y with roles X::y and A::x)\ PackageMerge to package P1

Perform a merge at package P2, you end up with

Class X (with X::y property)\ Class Y (with Y::x property)\ Association A (with A::x property and memberEnd pointing to X::y, A::x, Y::x)

eclipse-uml2-bot commented 7 hours ago

By Kenn Hussey on Jul 11, 2011 22:38

This should be addressed as a side-effect of adopting UML 2.4(.1).

eclipse-uml2-bot commented 7 hours ago

By Kenn Hussey on Jun 04, 2012 09:29

Turns out that this was not fixed as a side-effect of adopting UML 2.4(.1). :(