If you have existing modeling tools which were created with the previous version of Obeo Designer, the recommended procedure to make them compatible with the latest release is to migrate them step by step on all intermediate major releases of Obeo Designer. For example, to migrate modeling tools defined using Obeo Designer 7.0 to Obeo Designer 9.0, you should first migrate them to Obeo Designer 8.0, then to 8.1, and finally to 9.0.
The actual migration between two successive major versions N and M involves the following steps:
odesign
files) and save them back (you will need to make some change in the file to make it saveable; anything will do). This will automatically migrate the VSM data into the format of version M. Note: once this is done, you should never try to open the migrated VSM with version N (or earlier) of the software. Doing so is unsupported and may lead to unexpected behavior.MANIFEST.MF
file(s) of your modeler, update the version range for the dependencies to Sirius plug-ins so that the minimum version corresponds to the version in Obeo Designer M. This will guarantee your modeler (whose VSM is now incompatible with earlier versions of Sirius) can not be installed in environments which would not be able to use it correctly.Some additional tasks have to be performed to migrate existing modeling tools created with Obeo Designer 6.2:
.odesign
file) with Obeo Designer 7.0;MANIFEST.MF
file:
fr.obeo.dsl.common.acceleo
),fr.obeo.dsl.viewpoint
-> org.eclipse.sirius
),plugin.xml
file, replace reference to fr.obeo.dsl.viewpoint.componentization
by org.eclipse.sirius.componentization
.Activator.java
), replace all the references to proprietary source code by the corresponding open source packages:Before:
After:
.odesign
file have to be replaced by the appropriate query mechanism:var:
, feature:
and service:
);