Community
Participate
Working Groups
Papyrus-based applications such as Papyrus-RT may sometimes need to install their own EFactory instances in the resource set's package registry to have a custom implementation of the UML metamodel instantiated with custom behaviour/API. This means that all loci of element creation in Papyrus must use the registered package to create new UML model elements, not just invoke the UMLFactory.eINSTANCE static instance. One such locus is the CreateEditBasedElementCommand, which currently uses the static factory to create new model elements. This is used by, at least, the Model Explorer's "New Child" menu. I set this as blocking the Papyrus-RT bug for the custom UML-RT implementation of the UML metamodel because that will be useless without fixing this element creation behaviour in Papyrus.
New Gerrit change created: https://git.eclipse.org/r/85148
Gerrit change https://git.eclipse.org/r/85148 was merged to [streams/2.0-maintenance]. Commit: http://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/commit/?id=cf3a9c9d3b1d9d2f73ec8fbd4762b804e5848ab3
New Gerrit change created: https://git.eclipse.org/r/85158
Gerrit change https://git.eclipse.org/r/85158 was merged to [master]. Commit: http://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/commit/?id=5f62e7c6b9c1e92791afab32444ce573315415ec
(In reply to Eclipse Genie from comment #2) > Gerrit change https://git.eclipse.org/r/85148 was merged to > [streams/2.0-maintenance]. (In reply to Eclipse Genie from comment #4) > Gerrit change https://git.eclipse.org/r/85158 was merged to [master].