Skip to main content
Jump to: navigation, search

Kitalpha/technical/migration

< Kitalpha‎ | technical
Revision as of 09:31, 23 October 2018 by Benoit.langlois@thalesgroup.com (Talk) (Kitalpha 1.2.x to 1.3.x)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

General procedure of migration

For any new version of Kitalpha it is strongly advised to generate all the artifacts of a viewpoint. Indeed, if the textual description does not change, the implementation can change or the generation adjusts implementation when used APIs change.

Specific migration of Kitalpha releases

Kitalpha 0.5.x to 1.0.x

- Apply the general procedure of migration.
- Impact on the development environment: the Eclipse version evolved from Juno to Mars.
- The generated model APIs for viewpoints still conform to EMF 2.8.3 (Eclipse Juno).

Kitalpha 1.0.x to 1.1.x

- No migration impact.Only regenerate the API with the Viewpoint DSL editor.

Kitalpha 1.1.x to 1.2.x

- No migration impact.Only regenerate the API with the Viewpoint DSL editor.

Kitalpha 1.2.x to 1.3.x

For Viewpoint DSL, the query language migrated from Acceleo to AQL, especially for the diagram descriptions.
Example of migration in Viewpoint DSL/Diagram:

  • before Kitalpha 1.3.0: Label { content: "MyClass " + "<%name%>" + "." police: black }
  • from Kitalpha 1.3.0: Label { content: "MyClass " + "aql:self.name" + "." police: black }

Back to the top