Bug 487999

Description Laurent Fasani 2016-02-18 05:46:45 EST

Below is an extract of the MM_registration_in_VSM_spec.textile created in https://git.eclipse.org/r/66188 (bug 481849).

h3. Help specifier have/get the right meta-models

*VSP dependencies*
The "Create VSP" wizard has an new page to allow user choosing the meta-models. This page allows "Add from registry" and "Add from workspace" capabilities.
The added meta-models are automatically set as dependency in the VSP manifest.
The UI is the same as current meta-models propertyTab without "select from File" button.

*RepresentationDescription*
As indicated above, the available MM are those in "§Available Meta-models of RepresentationDescription":#MM_in_RepDesc.[cf below]
but, if the odesign belongs to an VSP and if the MM has not been set as VSP dependency, in both cases "Add from Registry" and "Add from workspace", it is possible to tick a "Display all MM" check box to select among all available MM for VSP.
Once selected, the MM is automatically added as dependency of the VSP.

When creating a RepresentationDescription, one of the first mandatory steps to do should be to set the meta-models.
To help, a dialog box is displayed to allow user choosing the meta-models. The dialog box content is the same as new the meta-models propertyTab.
[...]

h3(#MM_in_RepDesc). Available Meta-models of RepresentationDescription

When selecting a meta-model for a RepresentationDescription, the only available ones should be those in the scope of the odesign.
* If the odesign is *owned by a VSP*, the available MM are those accessible in the *classPath of the VSP*.
* If not, the available MM are those available in **deployed plug-ins** and **opened projects**.
The meta-models defined as ecore file are not candidate any more.


This ticket is about adding the UI described above in *RepresentationDescription* and *RepresentationDescription* sections