Bug 544269 - [ControlMode][Profile] ProfileApplication tagged "duplicatedProfile" must be read-only
Summary: [ControlMode][Profile] ProfileApplication tagged "duplicatedProfile" must be ...
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 4.2.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 434205
Blocks:
  Show dependency tree
 
Reported: 2019-02-08 04:45 EST by Vincent Lorenzo CLA
Modified: 2019-02-08 04:45 EST (History)
0 users

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 Vincent Lorenzo CLA 2019-02-08 04:45:59 EST 
When Profiles are applied on a Model, when the user creates subresources (ControlMode), Profile application are also propagated to the new roots of created resources, with an EAnnotation (duplicatedProfile). 
I propose such profiles be considered as read-only by Papyrus, from the point of you of the main model, but also from the point of view of the subresource itself, in order to avoid trouble with required stereotypes (Extension#isRequired=true) (Bug 543303) . So the goal of this bug is to ensure duplicate Profile Application can't be removed by the user to avoid bugs latter.