Bug 511456 - [Tooling] Prohibit UML-RT stereotypes to be applied manually
Summary: [Tooling] Prohibit UML-RT stereotypes to be applied manually
Status: NEW
Alias: None
Product: Papyrus-rt
Classification: Modeling
Component: tool (show other bugs)
Version: 0.8.0   Edit
Hardware: PC Windows 7
: P2 normal
Target Milestone: 1.0.2   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: depends_on_papyrus
Keywords:
Depends on: 462337
Blocks:
  Show dependency tree
 
Reported: 2017-02-01 06:41 EST by Peter Cigehn CLA
Modified: 2017-10-17 14:35 EDT (History)
3 users (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 Peter Cigehn CLA 2017-02-01 06:41:58 EST 
Eventually when we have all the proper tooling in place for Papyrus-RT, there should not be a need for any end-user to manually apply any of the UML-RT stereotypes. This is tracking bug, that tracks a bug in Papyrus that proposes a generic mechanism where it should be possible to tag stereotypes to only be possible to be applied programmatically, i.e. by the tooling, and they should not be available in the list of applicable stereotypes when manually trying to apply a stereotype.

This is to ensure that users cannot "by mistake" create inconsistent/incomplete/incorrect UML-RT models, which instead should be created, being guided and using the appropriate Papyrus-RT tooling. 

Such a mechanism can of course be useful for any DSML tooling built on top of Papyrus-RT and UML-RT as well.
Comment 1 Simon Redding CLA 2017-05-15 09:26:03 EDT 
Moving to future as the depends on Papyrus bug will not be addressed in time.
Comment 2 Christian Damus CLA 2017-05-19 08:52:56 EDT 
Pulling back into 1.0 as we have scheduled the blocking Papyrus bug now for Oxygen.
Comment 3 Christian Damus CLA 2017-05-25 11:14:57 EDT 
Postponing to Oxygen.1.  It would entail too extensive a new feature and API development at this stage of the RC ramp-down.
Comment 4 Ernesto Posse CLA 2017-10-17 14:35:37 EDT 
Mass changing all 1.0.1 bugs to target milestone 1.0.2, because Bug 520039 depends on Bug 526168 which depends on Bug 526167 which modifies plugin MANIFEST files and therefore requires a new service version number in accordance to the guidelines at https://wiki.eclipse.org/Version_Numbering#When_to_change_the_service_segment. Hence the solution to these bugs must be merged as a new version (1.0.1) and therefore all old 1.0.1 bugs should become 1.0.2.