Community
Participate
Working Groups
The UML export wizard splits out EPackages into separate resources when converting .ecore models with one main root package having several nested sub-packages. Also, there should be an option to specify referenced models from that wizard.
Yes, that second point is particularly important: a genmodel knows about references to dependent genmodels, so it shouldn't be necessary to reconvert the dependent ecores that were already converted to UML.
Created attachment 67114 [details] exporter updates without reference changes.
Created attachment 67166 [details] missing string
Created attachment 67344 [details] locate primitve types
Changes regarding nested packages have been committed. Providing support for referenced models isn't possible (i.e. is really difficult) when exporting to UML because UML resources use UUIDs. Hence, we will not address that issue at this time.
The changes are available in the 2.1M7 build.
Created attachment 69158 [details] update patch for procesing nested packages.
Small change required to fix nested packages. We don't need to call super for isValidPackage since it checks for nested classifiers. Also, we are concerned about the eEackage hierarchy not the genPackage. Kenn, please look at last patch.
The fix has been committed to CVS.
The fix is available in build 2.1RC1b.
Move to verified as per bug 206558.