| Re: [mdt-papyrus.dev] [PROVENANCE INTERNET] Re: [PROVENANCE INTERNET] Papyrus plan for managing GMFT dropout of therelease train |
|
Hi, For anyone interested here is the massive patch that will provide the switch to the internal fork [1] Since there is an inheritance from all diagrams to the tooling.runtime, it will required to much work to have a diagram by diagram patch. So everything comes in one commit. Quentin and I are still making tests but it looks good. Regards, Benoit 1:
https://git.eclipse.org/r/#/c/89368/ De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de NOYRIT Florian Hi, For Oxygen M5 we will go for this option.
Until Oxygen release we will work in cooperation with the new GMF-Runtime team and GMF-Tooling team to eventually contribute patches to GMF-Runtime.
Best regards. /Florian De :
mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de MAGGI Benoit Hi, As everyone know GMFT Project announced that it will stop contributing to the release train. A short analysis showed that the part of Papyrus that is currently contributed to the release train has a strong dependency to
org.eclipse.gmf.tooling.runtime We tried to include the plugin in the Project GMF-Runtime/Notation (See [1]) but Papyrus is the only one with dependency to GMFT so it doesn’t really make sense to integrate the plugin in GMF-Runtime/Notation for only one project. The chosen option is to fork the plugin an reintegrate it in Papyrus to stay in the train. The new namespace will be
org.eclipse.papyrus.infra.gmfdiag.tooling.runtime The first patch may be found here [2] These are sad news but this is the best plan we have. If anyone has an objection/suggestion/improvement… ? It’s the last call before merging the new plugin and regenerating all the diagrams. Regards, Benoit 1:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=510616 2: https://git.eclipse.org/r/#/c/89368/ |