Objecteering ClearCase commands

Overview

The following commands are specific to the Objecteering ClearCase MDAC.

The ... command	is used to …
Apply label	attach a label to a unit version defined by a view.
History	open the History window of the current element.
Version tree	open the version tree window for the current element.
Properties	display an element's properties.
Diff-Merge models	compare or merge the current model with another stored model.

The "Apply label" command

This command allows you to attach a label to a modeling unit and any components it may have.

Figure 52. Applying a label

This command cannot be used to create new labels. The creation of new labels is carried out from the ClearCase interface.

The "Store the label for the whole session" tickbox allows you not to enter a label for all components. When labeling is carried out in depth, the label entered the time before is then re-used.

The "History" command

This command starts a history browser on the current element, to display event records.

For further information on this dialog box, please refer to the related ClearCase documentation.

The "Version tree" command

This command starts a version tree browser on the current element.

For further information on this dialog box, please refer to the related ClearCase documentation.

The "Properties" command

The "Properties" command is used to display an element's properties.

For further information on this dialog box, please refer to the related ClearCase documentation.

The "Diff-Merge models" commands

The "Diff-Merge models" command is used to select a model you wish to compare, select the ancestor model and customize the options used by the Diff-Merge tool. The model to be compared and the ancestor model can be retrieved in:

· another project

· a repository managed by Objecteering Multi-user, a ClearCase view or a simple directory containing a model in a form equivalent to that of the model in the repository

· a model, from a ClearCase label. In this case, all the project elements must bear the indicated label.

Note: Before carrying out a model merge, you must check-out those elements which are going to be modified by the merge. If you are running a comparison without a subsequent merge, this is not necessary.

This information is defined through a wizard containing three windows. The first window (shown in Figure 53 below) is used to select the model which is to be compared. Three choices are possible:

· Select Objecteering project: by selecting this option, the list which follows contains all the projects available on the Objecteering site.

· Select repository: by selecting this option, you can define the directory where the elements which are to be compared are stored.

· Select label: by selecting this option, you can indicate the label which will be used to retrieve the model.

Figure 53. Selecting the model to be compared

To continue with the next step, you must either select an Objecteering project from the list, define a directory in which the element which is to be compared can be accessed or select a ClearCase label. After doing this, click on the "Next" button to continue with the second step.

The second window (shown in Figure 54) is used to select the ancestor model. This second window behaves in the same way as the first.

Figure 54. Selecting the ancestor model

The selection of an ancestor model is optional. In order not to define an ancestor model:

· if the "Select Objecteering project" tickbox has been checked, no Objecteering model should be selected

· if the "Select repository" tickbox has been checked, the "Repository" field must be left blank

· if the "Select ClearCase label" tickbox has been checked, no ClearCase label should be selected

To continue with the final step, simply click on the "Next" button.

The third window (shown in Figure 55) is used to define Diff-Merge customization options.

Figure 55. Configuring the Diff-Merge

The ... parameter	is used to ...
Create merge arrows	create, in ClearCase, merge arrows between the current model and the model which is to be compared. For further information, please refer to the <<cleartool merge -ndata>> ClearCase command. This option is only available if the model to be compared isretrieved from a label (Select "ClearCase label" in the Step 1 window).
Log	indicate the log where information on all the modifications carried out by the Diff-Merge editor is stored. Environment variables in $(OBJING_PATH) form can be used in this field to define the location of the log file.
External editor for merging texts	indicate the external editor used to merge all note types (C++, Java, documentation, etc). Environment variables in $(OBJING_PATH) form can be used in this field to define the location of the external editor of your choice.
Options and arguments for merge editor	define the options and arguments of the editor used in the Diff-Merge of texts. According to the editor used, options and arguments can be different. Two variables must be used to represent the initial text and the text to be compared. $(LEFTFILE) represents the initial text, and $(RIGHTFILE) represents the text to be compared. Unlike MDAC parameters, you must not put two $ signs.
Merge result	define the file containing the result of the text merge. According to the editor used, the editor value can be different. For example, if the editor saves the result of the merge in the initial text, the $(LEFTFILE) value must be given to this parameter.

To activate the comparison between the current model and the model to be compared, simply click on the "Finish" button.

For further information on the Diff-Merge tool, please see "The Diff-Merge tool".