mkproject

Create a UCM project

APPLICABILITY

SYNOPSIS

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

[ -tit·le title ] [ -mod·comp component-selector[,... ] ]
-in folder-selector
[ -crm·enable ClearQuest-user-database-name ]
[ project-selector ... ]

DESCRIPTION

The mkproject command creates a UCM project. A project includes policy information and configuration information.

Projects are created in UCM folders. A folder or folder hierarchy should 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 representing the parent folder of a UCM 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.

See chproject for information on setting policy for a project.

Using Rational ClearQuest with UCM projects

Optionally, you can link a project to a Rational ClearQuest database. The schema of the ClearQuest database must be UCM-enabled, and your system must be configured for the correct schema repository. All ClearQuest-enabled projects in the same project VOB must link to the same ClearQuest user database.

See chproject for related information.

RESTRICTIONS

Identities: No special identity required.

Locks: An error occurs if any of the following objects are locked: the UCM project VOB.

Mastership: There are no mastership requirements.

OPTIONS AND ARGUMENTS

EVENT RECORDS AND COMMENTS. Default: Creates one or more event records, with commenting controlled by your .clearcase_profile file (default: -c). See 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.

SPECIFYING A TITLE FOR THE PROJECT. Default: The project's name, as specified by the project-selector argument.

-tit·le title

Specifies a project title applied to all projects created with this command. The title argument can be a character string of any length. Use double quotes to enclose a multiple-word title or a title with special characters.

SPECIFYING A FOLDER FOR THE PROJECT. Default: None.

-in folder-selector

Specifies a folder.

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

SPECIFYING MODIFIABLE COMPONENTS. Default: None.

-mod·comp component-selector[,... ]

Specifies the components that can be modified by this project.

SPECIFYING A LINK TO THE CLEARQUEST DATABASE. Default: None.

-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.

SPECIFYING THE PROJECT NAME. Default: A generated name.

project-selector

Specifies the project.

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

EXAMPLES

The UNIX 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 shell or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt. In Attache, cmd-context represents the workspace prompt.

NOTE: In the UNIX examples that follow, arguments and output that show multicomponent VOB tags are not applicable to ClearCase LT, which recognizes only single-component VOB tags. In this manual, a multicomponent VOB tag is by convention a two-component VOB tag of the form /vobs/vob-tag-leaf-for example, /vobs/src. A single-component VOB tag consists of a leaf only-for example, /src. In all other respects, the examples are valid for ClearCase LT.

Create a project in the RootFolder of the project VOB webo_pvob.

cmd-context mkproject -c "creating webo project release 1" \
-title webo_proj1 -in webo_projects@/vobs/webo_pvob webo_proj1@/vobs/webo_pvob

Created project "webo_proj1".

SEE ALSO

chproject, lsproject, mkfolder, rmproject