You can delete a specific version of a file, directory,
or project from a directory and from the database. Additionally, you
can delete a project hierarchy.
About this task
ccm del|delete -p|-project ([-scope (project_only |
project_and_non-project_members | project_and_subproject_hierarchy |
entire_project_hierarchy)] | [-r|-recurse [-h|-hierarchy]])
project_spec...
ccm del|delete ([-scope (directory_only |
directory_and_non-project_members | entire_directory_hierarchy)] |
[-r|-recurse [-h|-hierarchy]]) [-repl|-replace] [-t|-task task_spec]
object_spec...
- -h|-hierarchy
- Causes the operation to delete the entire project hierarchy. This
must be used with the -recurse option.
- object_spec
- Specifies the object to delete.
- -p|-project
- Specifies the project form of the command.
- project_spec
- Specifies the project to delete. See Project specification for details.
- -r|-recurse
- Specifies whether the delete operation recurses into directories
or subprojects. When the object is a project, the recursive subprojects
are also deleted. When the object is a directory, the recursive children
of the directory are also deleted. For any other type of object, this
option has no effect.
When using this option to hierarchically delete
objects, the following apply:
- For a project object, -recurse is
equivalent to specifying -scope project_and_non-project_members.
It deletes the project and its members excluding subprojects.
- For a project object, -recurse -hierarchy is
equivalent to specifying -scope entire_project_hierarchy.
It deletes the projects and its recursive members including subprojects.
- For a directory object, -recurse is
equivalent to specifying -scope directory_and_non-project_members.
It deletes the directory and its recursive children excluding subprojects.
- For a directory object, -recurse -hierarchy is
equivalent to specifying -scope entire_directory_hierarchy.
It deletes the directory and its recursive children including subprojects.
- For any other type of object, the option has no
effect.
- -repl|-replace
- Deletes an object and replaces it with its predecessor.
- -scope (project_only | project_and_non-project_members | project_and_subproject_hierarchy
| entire_project_hierarchy)
- Specifies the scope of the project deletion. The project_only scope
means that only the project and its root directory are deleted. The project_and_non-project_members scope
means that the project and any members except subprojects are deleted.
The project_and_subproject_hierarchy scope means
the entire project hierarchy including all subprojects are deleted.
- -scope (directory_only | directory_and_non-project_members | entire_directory_hierarchy)
- Specifies the scope for the deletion of any directory objects.
The directory_only scope means that only the directory
itself is deleted. The directory_and_non-project_members scope
means that the directory and any children under the directory except
subprojects are deleted. The entire_directory_hierarchy scope
means the directory and all its recursive children including subprojects
are deleted.
- -t|-task task_spec
- When you delete an object whose parent directory is read-only,
a new version of the directory is checked out automatically. This
option associates the newly checked-out directory with a task if the
object was deleted from a read-only directory. If the current task
is set and you do not specify a different task, the newly checked-out
directory is associated with the current task automatically. See Task specification for details.
Example
- Delete the sort.c file
and replace it with the previous version (output will differ from the
following examples).
ccm delete sort.c
Member sort.c-1
deleted from project ico_proj-1
- Delete a file sort.c.
ccm delete sort.c-1:csrc:J#1
- Delete a project.
ccm delete -p Project_delete-1:project:M#1
- Delete a project hierarchically and recursively.
ccm delete -p Project_Top-int:project:W#1
-recurse -h