Thank you Benoit,
I agree that a change like that in Neon will have ripple effects that may be difficult to handle, however, those changes seem feasible for Oxygen.
@All: Who decides whether or not (and when) everything related to SysML 1.1 will be moved to “extraplugins” (e.g. I still see the directory “sysml” in the “plugins” directory)?
@Benoit: I liked your idea of having a SysML1.4 viewpoint configuration (outside “papyrus.infra…”) with only the “SysML1.4” category.
Regards,
Mauricio
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de MAGGI Benoit
Envoyé : mardi 21 juin 2016 16:13
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [PROVENANCE INTERNET] Re: [mdt-papyrus.dev] [PROVENANCE INTERNET] [Viewpoints][SysML] default viewpointconfiguration
Hi Mauricio,
There is no good reason to keep it in default.configuration but if you remove it you should add a new category with the same name that can be referenced by SysML viewpoints.
2 solutions:
-
Add the category in each SysML viewpoint
-
Create a common SysML view point with only this category
The main concern is about not breaking the link between SysML viewpoints and the SysML category.
Regards,
Benoit MAGGI
Dear Papyrus Developers,
I would like to know if somebody has a good reason to not erase the view category “sysml” in the default.configuration [1]. In principle, nothing in “papyrus.infra” should reference or even mention anything directly related to SysML or
any other language that depends on the Papyrus infrastructure and UML.
[1] platform:/plugin/org.eclipse.papyrus.infra.viewpoints.policy/builtin/default.configuration
Mauricio Alférez, PhD
Research Engineer
Commission for Atomic Energy and Alternative Energies (CEA)
Direction of Technological Research (DRT)
Systems and Technology Integration Laboratory (LIST)
Software and Systems Engineering Department (DILS)
Model-driven Engineering for Embedded Systems Laboratory (LISE)