Community
Participate
Working Groups
It seems that profiles imported in the import tool are not usable. The extensions from Stereotypes to the UML Meta-Model elements are not valid along with the base_X property types. After an import of a super simple profile I cannot pass validation and so cannot use the profile without redefining all the extensions.
Commit f31d4c4 fixes the Profile import transformation. However, the conversion from source "uml::Class" to Papyrus "uml::DataType" is still fragile. We may need some real-world test models to ensure the validity of the transformation. Especially, the following use cases need to be tested: - Source definition must still work (i.e. we shoudln't need to redefine the profile before using it) - Forward profile migration must still work (i.e. source models on which the source profile is applied, should be properly migrated to target models with target profile). I cannot test this, because the profile reconnection is not available yet. - Elements referencing a source "uml::Class" must reference the Papyrus "uml::DataType" after the transformation (Currently, properties, generalizations and GMF Shapes have been updated) It may be simpler (safer) to support uml::Class in Papyrus Profile diagrams (In addition to uml::DataType), even if they are semantically equivalent (by implementation, at least). This bug is fixed, so let's move the discussion for further improvements to Bug 410987
Great, it works.
