7.8 Cleaning Up the Project

When your team finishes work on a project and releases or deploys the new software, you should clean up the project environment before creating the next version of the project. Cleaning up involves removing any unused objects, and locking and hiding the project and its streams. This process reduces clutter and makes it easier to navigate in the Project Explorer.

Removing Unused Objects

During the life of the project, you or a developer might create an object and then decide not to use it. Perhaps you decide to use a different naming convention, and you create a new object instead of renaming the existing one. To avoid confusion and reduce clutter, remove these unused objects.

To delete a project, stream, component, or activity, select the object in the Project Explorer, and click File > Delete. To delete a baseline, use the cleartool rmbl command.

Projects

You can delete a project only if it does not contain any streams. When you create a project with the Project Creation Wizard, the wizard also creates an integration stream. Therefore, you can delete a project only if you created it with the cleartool mkproject command, or if you first delete the integration stream. For more information on removing projects, see the rmproject reference page in the Command Reference.

Streams

You can delete a development stream or an integration stream only if all of the following conditions are true:

• The stream contains no activities.

• No baselines have been created in the stream.

• No views are attached to the stream.

In addition, you cannot delete an integration stream if the project contains any development streams. For more information on removing streams, see the rmstream reference page in the Command Reference.

Components

You can delete a component only if all of the following conditions are true:

• No baselines of the component other than its initial baseline exist.

• The component's initial baseline does not serve as a foundation baseline for another stream.

For more information about removing components, see the rmcomp reference page in the Command Reference.

Baselines

You can delete a baseline only if all of the following conditions are true:

• The baseline does not serve as a foundation baseline.

• The baseline is not a component's initial baseline.

• A stream has not made changes to the baseline.

• The baseline is not used as the basis for an incremental baseline.

For more information about removing baselines, see the rmbl reference page in the Command Reference.

Activities

You can delete an activity only if both of the following conditions are true:

• The activity has no versions in its change set.

• No view is currently set to the activity.

For more information about removing activities, see the rmactivity reference page in the Command Reference.

Locking and Making Obsolete the Project and Streams

To prevent a project or a stream from appearing in the Project Explorer, lock the object and use the obsolete option. The obsolete option hides the object.

1. In the Project Explorer, select the stream or project that you want to hide, and click File > Properties to display its property sheet.

2. Click the Lock tab, and select Obsolete. Click OK.

To see objects that you have made obsolete, click View > Show Obsolete Items in the Project Explorer.