|Re: Merging UML models with different profile versions [message #1775087 is a reply to message #1774825]
||Tue, 24 October 2017 13:06
|| Philip Langer
Registered: March 2015
Location: Vienna, Austria
if you include the bundle org.eclipse.emf.compare.uml2.papyrus (e.g. through feature org.eclipse.emf.compare.diagram.papyrus - "Model comparison (EMF Compare) - Papyrus support"), you will get partial support for profile migration (see bug 495259).
In particular, EMF Compare will then run through your models before the comparison and tries, for any stereotype application that where the stereotype definition can't be resolved, to find an available profile definition (EPackage) that provides the stereotype in the registry. If such a definition can be found, it'll migrate to the respective profile and stereotype applications to the found stereotype. If no definition can be found, the model is left unchanged. Profile definitions are searched based on the URI of the missing stereotypes package URI. See also org.eclipse.emf.compare.uml2.papyrus.internal.hook.ProfileMigrationHook.
Note that this only works for static UML profiles that are registered -- it doesn't work for profiles that live in the workspace.
Hope this helps!
Get professional Eclipse developer support:
Powered by FUDForum
. Page generated in 0.01384 seconds