Creating a project using an existing directory as its root directory

You can create a project by reusing a specified directory as its root directory. The project name is the same as the name of the specified root directory. This command is useful for dividing a large directory hierarchy within a single project into one or more subprojects.

About this task

ccm create -r|-root -t|-type project [-v|-version version] 
        [-platf|-platform platform] [-purp|-purpose purpose] 
        [-release release_spec] [-set|-path|-setpath absolute_path] 
        [-wa|-maintain_wa] [-nwa|-no_wa] 
        ([-cb|-copy_based] | [-lb|-link_based|-ncb|-not_copy_based]) 
        ([-rel|-relative] | [-nrel|-not_relative]) 
        ([-mod|-modifiable] | [-nmod|-not_modifiable]) 
        ([-wat|-wa_time] | [-nwat|-no_wa_time]) 
        ([-tl|-translate|-translation] | [-ntl|-no_translate|-no_translation])
        [-c|-comment comment_string] [-ce|-commentedit] 
        [-cf|-commentfile file_path] dir_spec
-c|-comment comment
Specifies to append a comment on all baseline projects and their members when they are checked in to the released state. The comment can contain more than one line and accepts backslash encoded values.

You can use this option with -commentedit and -commentfile. If you use the -commentedit option, the comment displays in the default text editor.

-ce|-commentedit
Specifies to start the default text editor to compose and edit the comment. The result saved from the text editor is used as the final comment. You can use this option with the -comment and -commentfile options.
-cf|-commentfile file_path
Specifies to use the contents of the specified file for the comment. If you specified -comment, it is appended to that comment. You can use this option with the -commentedit option.
-cf|-commentfile file_path
Specifies to use the contents of the specified file for the comment. If you specified -comment, it is appended to that comment. You can use this option with the -commentedit option.
-cb|-copy_based
Specifies that a work area is copy-based.
-lb|-link_based|-ncb|-not_copy_based
Makes the work area link-based. This option is available to UNIX users only. See the work_area command for more information.
-mod|-modifiable_wa
Specifies that files in the work area have permissions set so they are modifiable even if they are not checked out. The default is -nmod|-not_modifiable_wa.
new_project_spec
Specifies the name and version (optional) of the project to be created. The new_project_spec must be in one of the name forms:

The new_project_spec option is not a general project specification. You cannot use forms such as an object name form or query selection set reference form.

-nmod|-not_modifiable_wa
Specifies that files in the work area have permissions set so they are modifiable by default only if they are in a writable state, such as working. The default is -nmod|-not_modifiable_wa.
-ntl|-no_translate|-no_translation
Specifies that ASCII files in the work area are copied between Windows and UNIX without newline translation. The default is -tl|-translate.
-nrel|-not_relative
Specifies that any work area is located on an absolute path. The default is for the new project to use the same relative setting as the project being checked out.
-nwat|-no_wa_time
Specifies that the new project does not have a maintained work area. Use the work area command if you want the project to have a maintained work area later. The default is -nwat|-no_wa_time.
-platf|-platform platform
Specifies the platform for the new project. The platform must be a valid platform name. The platform choices are listed in the %CCM_HOME\etc\om_hosts.cfg file (Windows) or $CCM_HOME/etc/om_hosts.cfg file (UNIX) in your Rational® Synergy installation. If the option is not specified, the default is not to set a platform.
-purpose purpose
Specifies the purpose for the new project. Set the purpose to the name of a defined purpose that is valid for the specified release. Use the project_purpose -show command to list valid purposes.
If this option is not specified, and you are in the developer role, the default is Insulated Development. If you do not specify this option, and you are in the build_mgr or ccm_admin role, the default is Integration Testing.
-rel|-relative
Specifies to locate the work area on a path relative to the parent project path.
-release release_spec
Specifies the release for the new project. You can set the release_spec to a single release that is defined and active. See Release specification for details.
Projects must have a release value because project groupings and corresponding process rules must be associated with a release. Manual update properties are not supported.
-set|-path|-setpath absolute_path
Specifies the work area path for the copied project. Set the absolute_path to an absolute path that you can see and modify. If not specified, the default work area path uses the current wa_path_template and project_subdir_template.
-tl|-translate|-translation
Specifies to perform newline translation of ASCII files when the files are copied between a Windows client and UNIX server, or between a UNIX client and a Windows server.
-v|-version version
Specifies the version to use for the new project.
-wa|-maintain_wa
Specifies that the new project has a maintained work area. The default is -wa|-maintain_wa.
-wat|-wa_time
Specifies that the files in the project work area use timestamps. The timestamps show the time the files were copied into the work area, rather than their modification time. The default is -nwat|-no_wa_time.

Example


Feedback