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.
When you work in Rational® ClearCase and you compare or merge versions of a model, the ClearCase Type Manager opens Rational Software Modeler to complete the model comparison or merge. However, the Compare Editor or Merge Editor might not have focus in the product. To compare or merge the model, click the Compare Editor or the Merge Editor.
By default, a ClearCase request for a model comparison or merge opens Rational Software Modeler. 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 Modeler, 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.
- Click OK.
When a model comparison or merge cannot find a custom profile (.epx file), a window opens that lists the resource path that is used to find the custom profile. The path can have four forms, and each form requries a different workaround.
Relative form - <file name>.epx
In this case, the model comparison or merge is looking for the .epx file in the same directory as the .emx file. To work around this issue using a Concurrent Version System (CVS), base ClearCase, or a view on a shared Unified Change Management (UCM) stream, you must update the view and refresh the custom profile. To work around this issue using a view on a private UCM stream, you must obtain the .epx file and copy it into your workspace.
Platform-relative form - platform:/<resource>/<projectname>/<file name>.epx
In this case, the workspace that started the model comparison or merge must contain the project that contains the .epx file. To work around this issue using CVS, base ClearCase, or a view on a shared UCM stream, you must update the view and refresh or import the project that contains the custom profile. To work around this issue using a view on a private UCM stream, you must obtain the .epx file or project and copy it into your workspace.
Path reference form - file://c:/<file path>/<file name>.epx
In this case, the resource path points to a specific directory for the .epx file. To work around this issue, ensure that the custom profile is located in the specified directory.
Pathmap form - pathmap://MAPVAR/<file name>.epx
In this case, the pathmap variable MAPVAR must point to the directory that contains the .epx file. To set the MAPVAR variable, complete the following steps:
- Click Window > Preferences.
- Expand Modeling and click Path Maps.
- Click New.
- Create a variable named MAPVAR that points to the directory that contains the profile.
When you compare or merge binary files, the state of the files in the configuration management system might not be reflected. To determine which binary files you should carry forward, use the version numbers in the file headers. You can examine the file headers using the ClearCase Version Tree Browser, or an equivalent tool for a Concurrent Version System (CVS).
Return to the main readme file