Using the Change Explorer to examine the changes in a change set

Use the Change Explorer view to examine the individual changes in a change set.
About this task

The Change Explorer view lists the contents of a change set and provides ways for you to examine each item in the change set and compare any of those items with the same item in another change set.

The Change Explorer view has two display modes: click the View as change sets icon toolbar icon to display changes as change sets, or click the View as file tree icon toolbar icon to display changes as folders and files.

You can pin a Change Explorer view to preserve its contents. To pin the view, click the Pin view icon toolbar icon. New Change Explorer views will open in a new instance.

To view a change set in the Change Explorer view:

  1. Navigate to the change set in the History view of a component. For more information, see Viewing or editing the change history of a component.
  2. Right-click the change set and click Open in Change Explorer. You can select multiple change sets to view their combined effect.
  3. Expand the change set to see the files and folders it contains.
  4. Right-click a file and choose an operation to initiate on it. Supported operations include:
    • Open in Compare Editor opens the "before" and "after" versions of the file in the Eclipse compare editor.
    • Show History opens a History view of the selected file.
    • Annotate opens an annotated view of the selected file. For more information, see Viewing annotations.
    • Compare With opens a window in which you can choose a baseline, workspace, or stream to search for another version of the file to compare with the one in the change set.
    Note: Change sets can include files that are not in your repository workspace. Operations such as Open in Compare Editor and Compare With require a workspace-relative path name before they can open a file, and will display a Resolve Paths window in which you can specify another workspace to search for the path name.

Feedback

Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug