When a sync message is created, the tool may also create an execution and a reply message. This reply message must target the original element from which the sync message is starting.
In PR #410, an issue was identified when the sync message is going out of an execution:
The fix should probably be located there: org.eclipse.papyrus.uml.interaction.internal.model.commands.InsertMessageCommand.createAutomaticReplyMessageCommands(Supplier, Supplier, Supplier, IntSupplier, IntSupplier) at line 660:
When a sync message is created, the tool may also create an execution and a reply message. This reply message must target the original element from which the sync message is starting.
In PR #410, an issue was identified when the sync message is going out of an execution:
The fix should probably be located there: org.eclipse.papyrus.uml.interaction.internal.model.commands.InsertMessageCommand.createAutomaticReplyMessageCommands(Supplier, Supplier, Supplier, IntSupplier, IntSupplier) at line 660:
Shape receiverShape = diagramHelper().getLifelineBodyShape(getTarget().getDiagramView().get());