| Summary: | Static version of the Standard UML profile | ||
|---|---|---|---|
| Product: | [Modeling] MDT.UML2 | Reporter: | Yann Tanguy <yann.tanguy> |
| Component: | Core | Assignee: | Kenn Hussey <Kenn.Hussey> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | bruck.james, Kenn.Hussey |
| Version: | 2.2.0 | Keywords: | plan |
| Target Milestone: | M4 | Flags: | Kenn.Hussey:
juno+
|
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | Compliance | ||
| Bug Depends on: | |||
| Bug Blocks: | 296328 | ||
|
Description
Yann Tanguy
I'm not sure it makes sense for the "standard" profile to be static, since its stereotypes are really nothing more than labels (it seems like overkill for code to be generated for them...). The standard profile does not need to be static for itself. But when you try to create a profile the reference UML::Standard and to make this new profile static, you are are to indicate the model generators (*.genmodel files) for any profile or metamodels (uml...) that is referenced by your new profile. I have created a static version of SysML. Due to inheritance links between SysML and Standard I had to create a static version of Standard. I thought such static version of uml::standard, would be at a better place in the Eclipse UML2 plugin. Maybe there is a better way to create static profiles, without having referenced profile being static too. Static implementations of the L2 and L3 profiles will be provided as part of adopting UML 2.4(.1). Static implementations of the UML 2.4 profiles have been committed to git. |