Community
Participate
Working Groups
Bug 400511 discusses a wizard for importing models from the Eclipse Workspace into a repository. The opposite operation is also needed: exporting models from the repository to the workspace. However, unlike the import wizard, the UI of the export wizard should be simpler. Unlike the import wizard, where path mappings are optional, the user must specify mappings to paths in existing projects. It cannot be expected that the resource paths in the repository have any kind of correlation to what is in the workspace, if the repository even uses resource folders. Thus, the export wizard should make no assumptions and requires the user to specify resource paths in projects that already exist; the wizard should not be concerned with creating projects, of whatever natures may be contributed by installed plug-ins. Also, the option to export all objects from the repository into one resource is likely not practical and should not be offered.
I can work on this.
r10435 on the cdo_kepler branch has a model export wizard to export models from a repository to the workspace. This includes a refactoring of the import wizard core and UI components for re-use of: * analysis of model cross-reference dependencies * mappings to paths in the import/export destination * validation Note that, whereas in the import of models the user is warned when models that depend on a model being imported are not also imported, in the export case the warning is when dependencies are not also exported (models referenced by models being exported). One limitation currently of the export to workspace is that it does not search the repository for models that depend on the models to be exported. A brute-force search is not feasible (loading the entire repository content from the server!) and it is far from clear that the analysis can be accomplished with a server-side query. This could use more investigation post Kepler. To simplify the import/export workflows, drag-and-drop between the Project Explorer and Model Repositories view is now supported. In particular, dragging models from a repository to the workspace pre-populates the path mappings based on the target of the drop. Otherwise, when the export wizard is invoked from the context menu, the wizard doesn't guess where the user wants to export to and the user has some tedious data entry to do.
The Model Export wizard has been merged to trunk in r10489.
