Community
Participate
Working Groups
I will attach a model to reproduce the bug in few minutes
Currently, no idea how to reproduce the initial bug on Papyrus 4.2.0... but I'm sure this bug exists...
On Oxygen : 1. Create a new Model 2. Create 3 package p1, p2, p3 3. Apply SyML Block profile on the root model 4. Create a Class Class1 in p1 and stereotype it Block 5. Save 6. Create a SubModel from p1 (a new file p1.uml will be created after the save action) 7. Create a SubModel from p2 (a new file p2.uml will be created after the save action) 8. Save 9. move Class1 from p1 to p2 10. Save -> open p1.uml and p2.uml as text : Class1 is stored in p2.uml, but the Stereotype Application Block is still in p1. This bug seems not reproductible on Papyrus 2018-12.
This bug seems fix, but we must provide JUnit tests for it. We should tests the decoration model (Stereotype Application stored in an external file) in the same time than the Controlmode.
New Gerrit change created: https://git.eclipse.org/r/135240
In fact, it is not fixed. It works only for moved elements, but not for their children. Moving a stereotyped classes which contains stereotyped properties, from a given resource to another one won't work propertly. The model is still valid, you can open/close it without problem, but the stereotypes applied on the properties are still stored in the initial resource.
New Gerrit change created: https://git.eclipse.org/r/136347
New Gerrit change created: https://git.eclipse.org/r/136361
*** Bug 529243 has been marked as a duplicate of this bug. ***
postponed 6.0.0