[ –pol/icy policy-keyword[,...] ] [ –npo/licy policy-keyword[,...] ]
[ –spo/licy policy-keyword[,...] ]
[ –model { SIMPLE | DEFAULT } ]
[ –crm/enable ClearQuest-user-database-name [–con/nection crm-connection ] ]
[ –bln/ame_template baseline-naming-template ]
[ project-selector ... ]
The mkproject command creates a project. A project includes policy information and configuration information.
Projects are created in folders. A folder or folder hierarchy must be in place before you create a project. If no folder exists, you can specify RootFolder as the folder selector with the –in option. RootFolder is a predefined object that represents the parent folder of a folder hierarchy. See mkfolder for more information.
Projects maintain a list of components that can be modified within the project. You can specify these with the –modcomp option. Streams in the project can make changes, such as checking out files, only in modifiable components; all other components are read-only.
The basic UCM process uses an integration stream and multiple development streams in a project. However, small teams of developers working together closely may prefer a single-stream project. You can create a project with single or multiple streams by using the –model option with keywords SIMPLE or DEFAULT. To create a single-stream project, your UCM VOBs and PVOBs must be at feature level 3 or greater.
You can set or unset projectwide policies, such as specifying that views attached to the integration stream must be snapshot views. Policies are identified by their keywords. Table 1 describes these policies and lists the keywords used to set them. For more information about setting policies, see the IBM Rational ClearCase Guide to Managing Software Projects.
By default, baseline identifiers are made up of two parts: a user-specifiable root name and a generated, unique numeric extension. Establish a meaningful baseline naming convention within a project. You can do so by using the option –blname_template. For more information about baseline names, see mkbl.
When you create baselines, UCM replaces commas with underscores in the baseline name.
You can specify the project as a simple name or as an object selector of the form [project:]project-name@vob-selector, where vob-selector specifies a project VOB (see the cleartool reference page). If you specify a simple name and the current directory is not a project VOB, this command assumes the project resides in the project VOB that is associated with the current view. If the current directory is a project VOB, that project VOB is the context for identifying the project.
The project name must be unique within the PVOB. All UCM objects share the same namespace. You'll get an error if the name you provide collides with the name of an existing UCM object, for example, a component.
The UNIX system and Linux examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.
The Windows examples that include 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 UNIX system and Linux shells or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.
cmd-context mkproject -c "creating webo project release 1" \
-in webo_projects@\webo_pvob webo_proj1@\webo_pvob
Created project "webo_proj1".
cmd-context mkproject -nc -modcomp comp1 -in RootFolder ^
-blname_template project,component,date CQ_ASP_V6.0