Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "VIATRA/Releases/MigrationTo1.2"
(Added manual rename tasks) |
|||
| Line 18: | Line 18: | ||
* Maven builds are not migrated. | * Maven builds are not migrated. | ||
| − | * | + | * Deprecated API [[https://www.eclipse.org/viatra/javadoc/releases/incquery-1.1.0/deprecated-list.html in EMF-IncQuery 1.1.0]] are removed in 1.2.0. These API usages have to be migrated manually. |
* Generated plugin extensions other than query specifications are regenerated, but the old ones are not removed. These shall be removed manually. | * Generated plugin extensions other than query specifications are regenerated, but the old ones are not removed. These shall be removed manually. | ||
* Type of static method calls (e.g. ''AdvancedIncQueryEngine.createUnmanagedEngine()'') shall be renamed manually. | * Type of static method calls (e.g. ''AdvancedIncQueryEngine.createUnmanagedEngine()'') shall be renamed manually. | ||
Revision as of 06:41, 10 March 2016
Migrating from EMF-IncQuery 1.1
From version 1.2 EMF-IncQuery is merged into the Viatra project as Viatra-Query. The merger involves the complete removal of org.eclipse.incquery namespace, thus making all code depenent on EMF-IncQuery incompatible with Viatra Query API. To ease the migration process, a migrator tool is included since Viatra 1.2 to reduce manual refactoring as much as possible.
The tool can be accessed in the 'Configure' context menu on projects where it is applicable.
Supported cases
- Migration of query projects (EMF-IncQuery 0.8.0-1.1.0)
- Updates project dependencies
- Updates query description files
- Updates query specification extensions
- Migration of Java and XTend projects
- Updates usage of EMF-IncQuery API
Remaining manual tasks after migration
- Maven builds are not migrated.
- Deprecated API [in EMF-IncQuery 1.1.0] are removed in 1.2.0. These API usages have to be migrated manually.
- Generated plugin extensions other than query specifications are regenerated, but the old ones are not removed. These shall be removed manually.
- Type of static method calls (e.g. AdvancedIncQueryEngine.createUnmanagedEngine()) shall be renamed manually.
- Renamed methods and fields are not migrated by the tool
- Schedulers.getIQEngineSchedulerFactory → Schedulers.getQueryEngineSchedulerFactory
- ExecutionSchemas.createIncQueryExecutionSchema → ExecutionSchemas.createViatraQueryExecutionSchema
- CRUDActivationStateEnum.APPEARED → CRUDActivationStateEnum.CREATED
- CRUDActivationStateEnum.DISAPPEARED → CRUDActivationStateEnum.DELETED