To prevent data corruption when you compare or merge models, you must not associate model file extensions with ASCII content. Model file extensions are associated with binary content by default. You must keep this default value.
To view the default file extensions with known content:
- Click Window > Preferences.
- Expand Team and click File Content.
When you accept a change from a version of a model, in the Merged result, the Enhanced Metafile (EMF) Tree view might not update to reflect the change. To work around this issue, view the change using the Explorer view or Diagram view.
When you compare versions of a model in a ClearCase® environment, you can compare a model version with its zero version. However, a model's zero version is an empty file that cannot be read by Enhanced Metafile (EMF) as a model. You should never compare a version of a model with its zero version, because the comparison will fail with errors.
By default, a ClearCase® request for a model comparison or merge opens Rational Software Architect. You can change the default behavior so that a version selector window opens instead of the product. However, the next time that you open Rational Software Architect, the default behavior is restored. To work around this issue, update the Compare/Merge Server settings each time that you want to change the default behavior.
To change the default behavior:
- Click Window > Preferences.
- Expand Workbench.
- Expand Compare/Patch.
- Expand Modeling Compare/Merge.
- Click Compare/Merge Server.
- Under Eclipse Auto Launch Configuration, click Clear.
- Click Apply then OK.
Return to the main readme file