Community
Participate
Working Groups
To produce a normative metamodel for the OMG for UML and SysML, the attached patch supports the following procedure: 1) open the model with the package merge maps for the desired compliance level with the "UML Editor". e.g.: for UML: L3.xmi for SysML: SysML-L3.xmi 2) select the toplevel package 3) menu: UML Editor > Package > OMG Merge... The option defaults have been set for producing merged artifacts for the OMG. 4) menu: UML Editor > Convert To > Metamodel 5) menu: UML Editor > Package > Unapply Profile... remove ecore. 6) create a separate folder where to save the model This step is important to avoid overwriting other artifacts, e.g., UML Infrastructure.xmi, Superstructure.xmi, UML4SysML.xmi, .... 7) menu: File > Save As... Select the separate folder. Additional cleanup steps may be required.
Created attachment 160990 [details] Patch for org.eclipse.uml2.examples.uml.ui and org.eclipse.uml2.uml.editor
Created attachment 161000 [details] New version of the patch for org.eclipse.uml2.examples.ui, org.eclipse.uml2.uml.editor Removed the rule in the original conversion that changed the visibility of associations to private.
This will need to be done in order to prepare the reference metamodel for UML 2.4(.1) in UML2 4.0.
As it turns out, this wasn't necessary in order to prepare the reference metamodel for UML 2.4. Instead, I used a separate model and merged the contents of the normative UML package (provided by the OMG as UML.xmi) into it.
