Bugzilla – Full Text Bug Listing
| Summary: | New article on migration from UML2 2.x API to UML2 3.0 API | ||
|---|---|---|---|
| Product: | [Modeling] MDT.UML2 | Reporter: | James Bruck <bruck.james> |
| Component: | Core | Assignee: | James Bruck <bruck.james> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Kenn.Hussey |
| Version: | 3.0.0 | Keywords: | plan |
| Target Milestone: | M3 | Flags: | Kenn.Hussey:
documentation+
Kenn.Hussey: review- |
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
James Bruck
Committed 20081005 Galileo M3 http://www.eclipse.org/modeling/mdt/uml2/docs/guides/UML2_3.0_Migration_Guide/guide.html James, Here are my comments: - The namespace for the metamodel is http://www.eclipse.org/uml2/3.0.0/UML - What is the 'Issue' column in the change summary tables? I don't see links to the issues... - Property::isNaviable() wasn't added... was it? I thought this operation existed previously. - Property no longer specializing TemplateableElement was not really a change in 2.2... this change more likely happened in the transition from pre-2.0 to 2.0 (but we didn't notice it until recently). - Loosing -> losing. - We don't need a stereotype to capture ClassifierTemplateParameter since this value can be stored in ClassifierTemplateParameter::default. - Issue 9143: Did you double-check that the label provider for operations adheres to the new syntax? - Issue 10354, 10536, 10537: Language used here (under impact) suggests the perspective is from IBM whereas the perspective should be from Eclipse. Note that for 10536 and 10537, there have been no changes (from an open source perspective) since the Eclipse implementation was actually ahead of the specification in this area. - Issue 9872: We need an icon for this new type... has one been made? - The namespace for the metamodel is http://www.eclipse.org/uml2/3.0.0/UML [James] .. silly me ... this has been updated. I was thinking: http://schema.omg.org/spec/UML/2.2/uml.xml which I will mention also. - What is the 'Issue' column in the change summary tables? I don't see links to the issues... [James] correspond to OMG issues ... I will provide links. - Property::isNaviable() wasn't added... was it? I thought this operation existed previously. [James] Very strange .. not sure how that crept in there. - Property no longer specializing TemplateableElement was not really a change in 2.2... this change more likely happened in the transition from pre-2.0 to 2.0 (but we didn't notice it until recently). [James] Yes but it made its way into this version and greatly impacts migration. I think it is worth mentioning here. - Loosing -> losing. [James] Right. - We don't need a stereotype to capture ClassifierTemplateParameter since this value can be stored in ClassifierTemplateParameter::default. [James] I don't agree. What if someone used both ClassifierTemplateParameter::default and defaultClassifier in the past? Silly but possible. The resource handler checks this case. - Issue 10354, 10536, 10537: Language used here (under impact) suggests the perspective is from IBM whereas the perspective should be from Eclipse. Note that for 10536 and 10537, there have been no changes (from an open source perspective) since the Eclipse implementation was actually ahead of the specification in this area. [James] There is impact on UML.uml which no longer merges the extra packages. This change might be relevant to the OCL component which uses the metamodels. - Issue 9872: We need an icon for this new type... has one been made? One has not been made yet but it has been requested. You will see the default star for now. Article on Wiki as of 20081106 |