Community
Participate
Working Groups
Steps to reproduce: 1. create 3 classes class1, class2, class3 2. drop class1 into a composite diagram 3. create property p1 (resp. p2) of type class2 (resp. class3) inside class1 4. create a port on property p1 5. try to move the port from p1 to p2, you are not allowed to do it 6. Go to the model explorer, go to class2 and move the port of class2 inside class3 7. Drop the port from the model explorer to the diagram (it will appear as a port of property p2) 8. Now we will see that the port is graphically attached to p1 and p2 (inconsistency) !!! 9. Try to hide the port on p1 (it will work, but the hide functionality is not supposed to work on a UML element that does not exist anymore!!).
Agreed. This bug is still valid in the context of Papyrus 3.0. 1] It shall be possible to move a port displayed on a port to another part. The impact of this operation is that the port shall now be owned by the type of the target part. If that part has no type then it shall not be allowed to drop the port onto the target part. 2] If the port owner gets changed (e.g., thanks to a drag and drop performed through the model explorer) then any displayed part typed by the Type owning that port shall be updated (i.e., the port representation shall be destroyed).
New Gerrit change created: https://git.eclipse.org/r/101699
Gerrit change https://git.eclipse.org/r/101699 was merged to [master]. Commit: http://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/commit/?id=dc7bec32ef1cbba17c97a77e1b28f7866b6747f3
