mkproject

Create a UCM project

APPLICABILITY

ClearCase UCM (cleartool subcommand)

SYNOPSIS

mkproject [ -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 ClearCase 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.

PERMISSIONS AND LOCKS

Permissions Checking: No special permissions required.

Locks: An error occurs if any of the following objects are locked: 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 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.

-tit·le title

Specifies a title for the project. 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.

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

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

Specifies the components that can be modified by this project.

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

project-selector

Specifies a project. If no project-selector is specified, a name is generated automatically.

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.

• Create a project in the RootFolder of the project VOB core_pvob.

cmd-context  mkproject -title "Java Parser" -in RootFolder@\vobs\core_pvob

Created project "Java_Parser_67890"

SEE ALSO

chproject, lsproject, mkfolder, rmproject