Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 348546

Summary: [Sysml 1.1][PropertyView] Different PropertyView for SysML Associations
Product: [Modeling] Papyrus Reporter: Yann Tanguy <yann.tanguy>
Component: SysMLAssignee: Project Inbox <mdt-papyrus-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: major    
Priority: P3 CC: benoit.maggi
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Yann Tanguy CLA 2011-06-07 08:21:34 EDT 
SysML associations should have their own property view :
- without end "owner" reference
- with SysML visibility management (navigable means owned by the Classifier / not navigable means owned by the association itself)

UML property view should not be shown for SysML associations.
Comment 1 Ansgar Radermacher CLA 2013-03-19 05:04:11 EDT 
The fundamental problem behind this error are subtle semantic differences between UML and SysML elements (in this case the Association) that are not distinguished by means of a stereotype. Papyrus currently uses ecore annotations to enable this distinction, but these are not visible for the user
Comment 2 Vincent Lorenzo CLA 2018-12-20 09:31:13 EST 
SysML 1.1 is no maintained anymore. We are closing the bug as wontfix.