Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "MDT/UML2/New and Noteworthy/Galileo"
(→Milestone 4) |
(→Milestone 4) |
||
| Line 1: | Line 1: | ||
| + | ==Milestone 5== | ||
| + | |||
==Milestone 4== | ==Milestone 4== | ||
Revision as of 18:42, 15 January 2009
Contents
Milestone 5
Milestone 4
The milestone was completed on Friday, 16 January 2009
Milestone 4 involved minor bug fixing and the application of patches contributed by the community. Some bugs of note are listed below:
232663 Avoid relative paths to models provided by plugins.
241411 No eGet, eSet, eIsSet, eUnset generated for certain redefined features.
242726 Genmodel copyright fields setting ignored for operations classes.
248008 Cache Adapter should complain very loudly when system property points to non-existent class.
256689 Missing generated package extension.
Milestone 3
This milestone was completed on Wednesday, 5 November 2008.
Migration to UML 2.2
The latest version of the UML superstructure specification (UML 2.2) is ready and in keeping in lock step with the changes at the OMG, the UML2 API has been updated.
* The version of UML as defined by the OMG is UML 2.2. * The latest version of the UML2 API is 3.0.0.
In M3 ...
+ The UML2 API was regenerated based on updated specification changes.
+ All metamodels from which the UML2 api is generated were updated.
+ Migration code was added to migrate previous versions of serialized UML to the latest.
+ A migration guide was created: http://www.eclipse.org/modeling/mdt/uml2/docs/guides/UML2_3.0_Migration_Guide/guide.html
Other Enhancements
A complete list of the enhancement requests resolved in this milestone can be found here.
Milestone 2
This milestone was completed on Wednesday, 24 September 2008.
Catching up to EMF
The UML2 project directly extends EMF and as such, must keep up with version number updates and feature updates concerning code templates in the EMF project. All version numbers were updated and code templates were updated.
Associations between Stereotypes
The PackageOperations.applyProfile() now takes into account associations between stereotypes in the same profile.
Creating associations between stereotypes really implies having properties typed by the DynamicEObject's representing the stereotype application.
The StereotypeApplicationCopier now more carefully considers the impact of associations during migration.
Other Enhancements
A complete list of the enhancement requests resolved in this milestone can be found here.