[mdt-papyrus.dev] Changes in the elementtypesconfigurations framework

[NOYRIT Florian <florian.noyrit@xxxxxx>]

Dear Papyrus contributors,

 

As explained in https://wiki.eclipse.org/Papyrus/Migration_Guide/Neon#Multiple_ClientContext, the loading, unloading and registration of elementtypesconfigurations in Neon has changed.

Now, the clientContext that the elementypesconfigurations must bind must be specified. This is a first step towards multiple context in Papyrus (e.g. one context for SysML, one context for UML, one context for RobotML…).

 

Although those contexts will somehow be linked to the viewpoint definition, in the meantime you can still use the Papyrus unique default clientcontext (namely “org.eclipse.papyrus.infra.services.edit.TypeContext” defined in org.eclipse.papyrus.infra.services.edit.internal.context.TypeContext)

 

All uses of this API have been migrated in Papyrus (except extra-plugins). External uses will have to migrate.

 

Best regards.

 

/Florian