Bug 544171 - [DecorationModel] ControlMode doesn't create new xxx.profileapp.uml when the initial model use the DecorationModel feature
Summary: [DecorationModel] ControlMode doesn't create new xxx.profileapp.uml when the ...
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: Confirmed
Keywords:
Depends on:
Blocks: 543489
  Show dependency tree
 
Reported: 2019-02-06 04:52 EST by Vincent Lorenzo CLA
Modified: 2019-02-08 04:15 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Lorenzo CLA 2019-02-06 04:52:17 EST
DecorationModel is the feature which allows to externalize the profile application
Steps to reproduce:
	1. Create a profile with a stereotype Ste1 extending Class
	2. create a model Model1 with a subpackage P1 and a Class Class1
	3. Apply the profile on the model
	4. Stereotype Class1 with Ste1
	5. Select the root model, Go in the Property View, Profile Tab, Select the applied profile and externalize it.
		-> a new resource is created Model.profileapps.uml which contains the stereotype application
	6. Create a sub model (Controlmode) from P1 in order to get P1.di/notation/uml files. 
			-> this action doesn't create a new resource P1.profileapps.uml to contain the externalized profile.
			
Please fixing the bug, check the move of UML element from a subresource to another. The stereotype applications of moved elements must follow the stereotyped elements AND the stereotype application of their children must follow them too of course. (see bug 543498)

look the method org.eclipse.papyrus.uml.decoratormodel.helper.DecoratorModelUtils.configure(ResourceSet). This method configure a specific StereotypeApplicationHelper and ProfileApplicationHelper to allow the externalization.
Comment 1 Vincent Lorenzo CLA 2019-02-08 04:15:21 EST
Please see bug 543489 instead of bug 543498