chproject

Modifies a UCM project

APPLICABILITY

ClearCase UCM (cleartool subcommand)

SYNOPSIS

chproject [ -c·omment comment | -cfi·le pname | -cq·uery | -cqe·ach | -nc·omment ]

{ [ -tit·le title ]
[ -amo·dcomp component-selector[,... ] ]
[ -to to-folder-selector ]
[ -reb·ase-level promotion-level ]
[ -policy policy-keyword[,...] ] [ -npolicy policy-keyword[,...] ]
[ -crm·enable ClearQuest-user-database-name | -ncr·menable ] }
project-selector ...

DESCRIPTION

The chproject command modifies one or more UCM projects. Use it for these tasks:

• Change a project's title
• Add one or more modifiable components to a project
• Move a project to another folder
• Change the promotion level required of a baseline before it can be used in a rebase operation.
• Set policy for a project.
• Enable or disable a project for use with Rational ClearQuest

Project Titles

Note that changing a project's title does not affect its name (its unique identifier). See rename for related information.

Adding New Components

Over time, a project's scope can broaden, and you may need to add writable components to the project's integration stream. The -amodcomp option allows you to add one or more modifiable components. Components can be added to project development streams with the rebase -baseline command.

Setting Required Promotion Levels for Recommended Baselines

A project's rebase level is defined as the minimum promotion level a baseline must have to be recommended in a rebase operation. For example, if ProjectA has three promotion levels, REJECTED, TESTED, and RELEASED (in ascending order), and TESTED in the rebase level, only baselines that are labeled TESTED or RELEASED are included in the project's list of recommended baselines. See rebase and setplevel for more information.

Project Policies

You can set or unset projectwide policies, such as specifying that views attached to the integration stream must be snapshot views. Policies are identified on the command line by their keyword. The following table describes these policies and lists the keywords used to set them.

Policy	Keyword
Recommend snapshot views for integration work. Dynamic views are suggested if this policy is not set.	POLICY_UNIX_INT_SNAP (UNIX platforms) POLICY_WIN_INT_SNAP (Windows platforms)
Recommend snapshot views for development work. Dynamic views are suggested if this policy is not set.	POLICY_UNIX_DEV_SNAP (UNIX platforms) POLICY_WIN_DEV_SNAP (Windows platforms)
Require a development stream to be based on the current recommended baselines before it can be used to deliver changes to the integration stream.	POLICY_DELIVER_REQUIRE_REBASE
Do not allow delivery from a development stream that has checkouts.	POLICY_DELIVER_NCO_DEVSTR

Using Rational ClearQuest with UCM projects

You can link or unlink a UCM project to a ClearQuest database with the -crmenable or -ncrmenable options. When you ClearQuest-enable a UCM project that contains UCM activities, for each UCM activity, a ClearQuest record of type UCMUtilityActivity is created and linked to the activity. This process is called activity migration. If you disable a link to ClearQuest, from a UCM project that contains activities, all its activities are unlinked from their ClearQuest records.

All ClearQuest-enabled projects in the same UCM project VOB must link to the same ClearQuest user database.

The -crmenable and -ncrmenable options display a summary of the number of activities that have been migrated or unlinked.

You are informed if activities cannot be migrated or linked because they are not mastered in the current UCM project VOB replica. If any are discovered, you are informed of the number of activities for which this is true and shown a list of replicas from which to run the command again to correct the problem.

Detecting and Correcting Incorrectly Enabled Activities

You can also use the -crmenable and -ncrmenable options to check for possible linking errors. If you believe that your ClearQuest-enabled project may contain activities that are not linked to a ClearQuest record, run the chproject -crmenable command. This scans all activities in the project, skipping activities that are already linked and migrating all activities that are not linked. To check for linked activities in projects that have been disabled for use with ClearQuest, run the chproject -ncrmenable. This removes links between activities as needed. See Managing Software Projects with ClearCase for further information.

PERMISSIONS AND LOCKS

Permissions Checking: None.

Locks: An error occurs if there are locks on any of the following objects: the project or the UCM project VOB.

Mastership: The project must be locally mastered.

OPTIONS AND ARGUMENTS

EVENT RECORDS AND COMMENTS. Default: Creates one or more event records, with commenting controlled by your .clearcase_profile file (default: -cq). See CUSTOMIZING COMMENT HANDLING in the comments reference page. Comments can be edited with chevent.

-c·omment comment | -cfi·le comment-file-pname |-cq·uery | -cqe·ach | -nc·omment

Overrides the default with the option you specify. See the comments reference page.

ASSIGNING A NEW TITLE.

-tit·le title

Specifies a new title for the project. The title argument can be a character string of any length. Enclose a title with special characters in double quotes

MOVING THE PROJECT TO ANOTHER FOLDER.

-to to-folder-selector

Moves one or more projects to the specified folder.The to-folder and project must have the same UCM project VOB.

folder-selector is of the form: [folder:]folder-name[@vob-selector] and vob is the folder's UCM project VOB.

CHANGING THE RECOMMENDED PROMOTION LEVEL FOR A REBASE OPERATION.

-reb·ase_level promotion-level

Changes the promotion level required for baselines to be recommended baselines in a rebase operation. For each component, the latest baseline in the integration stream at or above this promotion level is recommended.

SETTING PROJECT POLICY.

-policy policy-keyword

Activates the specified policy.

-npolicy policy-keyword

Removes the specified policy.

LINKING A PROJECT TO RATIONAL CLEARQUEST.

-crm·enable ClearQuest-user-database-name

Enables a link from the project to the specified Rational ClearQuest database. The schema of the ClearQuest database must be UCM-enabled, and your system must be configured for the correct schema repository.

-ncr·menable

Disables use of Rational ClearQuest.

ADDING TO THE LIST OF MODIFIABLE COMPONENTS FOR A PROJECT.

-amo·dcomp component-selector[,... ]

Adds one or more components to the project's set of modifiable components.

component-selector is of the form: [component:]component-name[@vob-selector] and vob is the component's UCM project VOB.

SELECTING A PROJECT.

project-selector ...

Specifies one or more projects to modify.

project-selector is of the form: [project:]project-name[@vob-selector] and vob is the project's UCM project VOB.

EXAMPLES

Examples including wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.

In cleartool single-command mode, cmd-context represents the command interpreter prompt. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt. In Attache, cmd-context represents the workspace prompt.

• Move the project Java_Parser_Project to the folder Java_Folder.

cmd-context  chproject -c "Project reorganization" -to Java_Folder@\vobs\core_projects
Java_Parser_Project_28174@\vobs\core_projects

Changed project "Java_Parser_Project_28174@/vobs/core_projects".

SEE ALSO

chbl, lscomp, lsproject, mkproject, mkcomp, rebase, rmproject