Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 348546 - [Sysml 1.1][PropertyView] Different PropertyView for SysML Associations
Summary: [Sysml 1.1][PropertyView] Different PropertyView for SysML Associations
Status: CLOSED WONTFIX
Alias: None
Product: Papyrus
Classification: Modeling
Component: SysML (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-07 08:21 EDT by Yann Tanguy CLA
Modified: 2018-12-20 09:31 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.