Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[UML Notation:005]: Message label #251

Closed
planger opened this issue Apr 28, 2018 · 3 comments
Closed

[UML Notation:005]: Message label #251

planger opened this issue Apr 28, 2018 · 3 comments
Assignees
Labels
prio_high High priority uml_notation Requirements related the which UML notation the new implementation should support

Comments

@planger
Copy link
Collaborator

planger commented Apr 28, 2018

The message label SHALL be shown as stated in the UML spec 2.5.1 (17.4.4.1). Note that when the message has a signature defined, the message name is the name of the when it is linked to a signature, the name of the message must be the name of the Operation or Signal refers by the signature.

@planger planger added uml_notation Requirements related the which UML notation the new implementation should support prio_high High priority labels Apr 28, 2018
@planger
Copy link
Collaborator Author

planger commented Jul 18, 2018

Please see #18

@planger
Copy link
Collaborator Author

planger commented Aug 9, 2018

Implementation via #337

@planger planger mentioned this issue Aug 10, 2018
4 tasks
rschnekenbu added a commit that referenced this issue Oct 17, 2018
- extend add/remove semantic listeners to get notifications on model
changes required for label updates
- small NPE coming from reorient message update

Change-Id: I31b346b998ca52014cd34966bda1a13a4a67b6a2
Signed-off-by: Remi Schnekenburger <rschnekenburger@eclipsesource.com>
rschnekenbu added a commit that referenced this issue Oct 19, 2018
- fix test issues: removing labels that prohibits some moves on self
messages.

Change-Id: Ie170814ce57b8b42a3b8026e0bd301454bbf6c4a
Signed-off-by: Remi Schnekenburger <rschnekenburger@eclipsesource.com>
planger added a commit that referenced this issue Oct 31, 2018
@planger
Copy link
Collaborator Author

planger commented Nov 5, 2018

I opened a new issue for the remaining label wrapping issues in #395

@planger planger closed this as completed Nov 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prio_high High priority uml_notation Requirements related the which UML notation the new implementation should support
Projects
None yet
Development

No branches or pull requests

2 participants