Community
Participate
Working Groups
Step to reproduce this bug : 1 - Create a class diagram 2 - Apply the SysML profile on the Model 3 - Create a class 4 - Apply the stereotype "Block" on this class 5 - Undo the last change The stereotype application is not removed but the class is removed.
Still doesn't work properly in 0.10.0: applying a stereotype triggers two commands.
Still present in 1.0.0. 1 - Create a class diagram 2 - Apply the SysML profile on the Model 3 - Create a class 4 - Apply the stereotype "Block" on this class 5 - Undo the last change => Nothing 6 - Undo the last change => the class is removed There is probably a problem on the refresh with stereotype see 393532
Patch on gerrit : https://git.eclipse.org/r/#/c/33368/ It will solve this problem using the same way as unapply stereotype. But there is still a lot of command for applying and unapplying stereotype Is there a reason for keeping all of them ? => maybe it will be a better solution to use org.eclipse.papyrus.uml.tools.commands.ApplyStereotypeCommand
Gerrit change https://git.eclipse.org/r/33368 was merged to [master]. Commit: http://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/commit/?id=9bc39e219e0e2204139ad062500e8ec52eeeb5f3
> Gerrit change https://git.eclipse.org/r/33368 was merged to [master]. As mentioned in the Gerrit review, this approach can only be a workaround. But since then, Bug 437898 and Bug 393532 have been fixed and the ApplyStereotypeRequest should be used instead of trying to build add-hoc notifications
> the ApplyStereotypeRequest should be used instead of trying to build add-hoc notifications Actually since the stereotype listener is now a resource set listener, this shouldn't even be required (But still probably a good idea)
This works as expected in the current version
