Community
Participate
Working Groups
Created attachment 236047 [details] Reproducible test case Here is a model migration use case & test case. Attached project has a slightly updated model compared to Bug 418478. The use case is; 1) a model+profiles exported from one UML tool (= not Papyrus) 2) create Papyrus runtime versions of needed profiles 3) import the model, now having locally applied profiles 4) switch to runtime profiles created in step 2 above (see Bug 408491) 5) remove locally applied profiles not needed This can also assist in understanding outstanding issues related to Bug 408491. Attached is a plug-in project containing the needed profile and a test model. 1) Generate the profiles plugin. 2) Restart. 3) Open the model in the "model" folder. It has an applied local XYZProfile (the same as in the generated plugin) plus an applied XYZDeployProfile. 4) Switch the XYZProfile to the runtime version of it, using the function described in Bug 408491. 5) Remove the XYZDeployProfile. (it is not needed by the model) After step 5 all applied stereotypes have vanished from the model.
I think this problem happens as a result of bug 408491. The profile switch, as currently implemented, is what actually corrupts the stereotype applications in the model. I don't think there's a new bug here; there is only the unfinished 408491.
I close this issue, which appears to have been fixed.