| [mdt-papyrus.dev] Papyrus 0.9: UML Diagram Common refactoring |
|
Hello all, Due to the new incoming features for Papyrus 0.9, we need to refactor the UML Diagram Common plug-in (Trunk only). This is a major change, which will impact all diagrams, and require diagram regeneration. This will take
a few days (Maybe less if we don’t meet any major issue J ), and to avoid conflicts, you should stop committing on the diagram plug-ins until this is finished (0.9/Trunk only). For your information, the modifications will include: -
New Abstract edit parts for *all* Papyrus EditParts. These edit parts will extend the GMF ones, and all Papyrus EditParts should extend them (Requires diagram regeneration) -
These new edit parts and the existing ones (NodeEditPart, ResizeableListCompartmentEditPart) will be moved to infra/gmfdiag/common -
The ui helpers from uml/utils will be moved to a gmf-specific plug-in (Either infra/gmfdiag/common or a new one) -
The constants associated to these helpers (VisualInformationPapyrusConstant) will be split between UML-specific ones and GMF-generic ones The impacted plug-ins are: -
Uml.tools.util -
Infra.gmfdiag.common -
Uml.diagram.* -
Sysml.diagram.* Except for the diagrams regeneration, this should not change anything. Depending on the difficulty to do this refactoring, more classes might move from uml.diagram.common to infra.gmfdiag.common. I’ll keep you informed. Thank you, Camille __________________________ Camille Letavernier +33 (0)1 69 08 00 59 -
camille.letavernier@xxxxxx CEA LIST - Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE) |