IBM Rational ClearCase - Configuration Specifications

Configuration Specifications

Under base ClearCase, each view is controlled by its associated configuration specification, commonly referred to as a config spec. This is a collection of rules (stored internally in a text file, but compiled to a more efficient form before use) that specifies what elements (files or directories) should be visible in a view, and which versions of these elements. When deciding which version, if any, of an element should be visible, ClearCase traverses the configuration specification line-by-line from top to bottom, stopping when a match is found. Earlier rules always take priority over later ones.

A typical configuration specification could look like this:

# Show all elements that are checked out to this view, regardless any other rules. element * CHECKEDOUT # If an element has a version on the 'module2_dev_branch', then the latest # version of this branch shall be the visible version in this view. element * .../module2_dev_branch/LATEST # For all files named 'somefile', regardless of location, always show the latest version # on the main branch. element .../somefile /main/LATEST # Use a specific version of a specific file. Note: This rule must appear before # the next rule to have any effect! element /vobs/project1/module1/a_header.h /main/proj_dev_branch/my_dev_branch1/14 # For other files in the 'project1/module1' directory, show versions # labeled 'PROJ1_MOD2_LABEL_1'. Furthermore, don't allow any checkouts in this path. element /vobs/project1/module1/... PROJ1_MOD2_LABEL_1 -nocheckout # Show the 'ANOTHER_LABEL' version of all elements under the 'project1/module2' path. # If an element is checked out, then branch that element from the currently # visible version, and add it to the 'module2_dev_branch' branch. element /vobs/project1/module2/... ANOTHER_LABEL -mkbranch module2_dev_branch

A configuration specification can also reference other configuration specifications using the 'include' statement.

Under ClearCase UCM these config specs still exist but do not need to be maintained or edited anymore by end-users or administrators.