Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 371123 - Introduce a mechanism to detect meta-model version compatibility
Summary: Introduce a mechanism to detect meta-model version compatibility
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: 0.9   Edit
Assignee: Alvaro Sanchez-Leon CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-09 14:05 EST by Alvaro Sanchez-Leon CLA
Modified: 2012-02-16 20:49 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alvaro Sanchez-Leon CLA 2012-02-09 14:05:43 EST 
it's necessary to detect compatibility among meta-model versions integrated within the different versions.

a later phase is to provide data migration options among major version changes.
Comment 1 Alvaro Sanchez-Leon CLA 2012-02-16 20:49:05 EST 
R4E core was updated to assign default values and application level version values for three sub models i.e. Group, Review, RuleSet.
An api was introduced to resolve detect compatibility of already serialised models against the current version of the application. 
  R4E core throws and exception when a serialised version is ahead of the current application
  R4E UI detects if the serialized version is below the version supported by the application if so the user is prompted to decide on converting the model to the same level as the application or to open it in Read Only mode (to prevent overriding a format that may prevent other users from opening it).