| Summary: | [Profile Diagram] Extension management ? Ambiguous Naming Convention? When two extensions are created for a same stereotype, they get the same name. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | alanusse Mising name <agnes.lanusse> | ||||
| Component: | Core | Assignee: | Vincent Lorenzo <vincent.lorenzo> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | 0.7.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
alanusse Mising name
Created attachment 172771 [details]
Screen View Ambiguous naming of extensions in Profile Diagram
I change the naming convention for the extension. This new convention looks like the association convention (cf page 18 from the UML Superstructure V2.2) : E_stereotypeName_metaclassName. To conclude the extension name is : E_stereotypeName_metaclassName, suffixed by a number. Done in r2102 *** Bug 318002 has been marked as a duplicate of this bug. *** *** Bug 318007 has been marked as a duplicate of this bug. *** |