how to delete a project
beginner
I hv created some projects in clearcase LT
Now I hv to delete one of these project
Can anyone tell me how to delete a project from clearcase LT
plz mention step by step
beginner
Assad Chaudhry
rmproject
Removes a project
DESCRIPTION
The rmproject command deletes one or more projects. All streams must be removed before deleting a project. You cannot delete a project that contains a stream.
RESTRICTIONS
Identities
You must have one of the following identities:
Locks
An error occurs if there are locks on any of the following objects: the project VOB, the project.
Mastership
(Replicated VOBs only) Your current replica must master the project.
OPTIONS AND ARGUMENTS
Event Records and Comments
- Default
- Creates one or more event records,
with commenting controlled by your .clearcase_profile file
(default: –nc). 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.
Confirmation Step
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.
- Remove
a project that contains a stream.
- Issue the rmproject command:
- Use lsproject –long to
see a detailed description of the project, including a list of any streams
contained by the project:
cmd-context lsproject –long html_parser
cleartool lsproject -l html_parser
project "html_parser"
07-Sep-99.11:24:27 by Bsmith
owner: bsmith
group: user
folder: parsers
title: html_parser
integration stream: html_parser_int
development streams:
html_parser_int
modifiable components:
default rebase promotion level: INITIAL
recommended baselines: - Remove the stream. The –force option bypasses the confirmation step.
- Reissue the rmproject command:
Luciano Azevedo
Brian Cowan
If you have EVER delivered in this project, ANY attempt to remove it is
doomed to failure.
Why?
Well, to remove a project, you have to remove all the streams.
To remove a stream, You have to remove all the activities and baselines
created in that stream as well as all the views associated with it..
To remove an activity, you have to remove all the versions in its change
set. (Simple, but tedious, "ct rmver -xhlink")
To remove a *baseline*, it cannot
- be a delivered baseline,
- be used by any other streams as a foundation
- be used by any other baselines as a "backstop."
The problem is that *all* delivers create, and then deliver, a baseline.
This baseline is -- by definition -- irremovable. So, any project where
a deliver has ever been completed cannot be removed.
The workaround is to lock the activities and streams associated with the
project obsolete, then lock the project itself obsolete. it will then at
least drop off the GUI's... If you do not plan on using the baselines
associated with the project, lock them obsolete as well.
Assad Chaudhry wrote:
> Please see http://www.ipnom.com/ClearCase-Commands/rmproject.html for
> more details
>
>
> rmproject
>
> Removes a project
>
>
> APPLICABILITY
>
> Product Command type
> ClearCase cleartool subcommand
> ClearCase LT cleartool subcommand
>
>
> Platform
> UNIX
> Windows
>
>
> SYNOPSIS
>
> *rmproj·ect *[ *–c·omment* /comment/ | *–cfi·le* /comment-file-pname/
> | *–cq·uery* | *–nc·omment* ] [ *–f·orce* ] /project-selector/ ...
>
>
> DESCRIPTION
>
> The *rmproject* command deletes one or more projects. All streams must
> be removed before deleting a project. You cannot delete a project that
> contains a stream.
>
>
> Projects Enabled for ClearQuest
>
> When you delete a project that uses the UCM-ClearQuest integration,
> the project is unlinked from its associated ClearQuest record, but the
> ClearQuest record is not deleted.
>
>
> RESTRICTIONS
>
>
> /Identities/
>
> You must have one of the following identities:
>
> * Project owner
> * Project VOB owner
> * *root* (UNIX)
> * Member of the ClearCase administrators group (ClearCase on
> Windows only)
> * Local administrator of the ClearCase LT server host (ClearCase
> LT on Windows only)
>
>
> /Locks/
>
> An error occurs if there are locks on any of the following objects:
> the project VOB, the project.
>
>
> /Mastership/
>
> (Replicated VOBs only) Your current replica must master the project.
>
>
> OPTIONS AND ARGUMENTS
>
>
> Event Records and Comments
>
> *Default*
> Creates one or more event records, with commenting controlled by
> your *.clearcase_profile* file (default: *–nc*). 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.
>
>
> Confirmation Step
>
> *Default*
> Prompts for confirmation that the specified project is to be deleted.
>
> *–f·orce *
> Suppresses the confirmation step.
>
>
> Specifying the Project
>
> *Default*
> None.
>
> /project-selector ... /
> Specifies one or more projects to delete.
>
> /project/-/selector/ is of the form
> [*project:*]/project-name/[@/vob-selector/], where /vob-selector
> /specifies the project's 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.
>
> * Remove a project that contains a stream.
> 1. Issue the *rmproject* command:
>
> /cmd-context/ *rmproject html_parser*
> Remove project "html_parser"? [no] *yes
> *cleartool: Error: Cannot remove project that has streams.
> cleartool: Error: Unable to remove project "html_parser".
>
> 2. Use *lsproject* *–long* to see a detailed description of
> the project, including a list of any streams contained by
> the project:
>
> /cmd-context/ *lsproject –long html_parser
> *cleartool lsproject -l html_parser
> project "html_parser"
> 07-Sep-99.11:24:27 by Bsmith
> owner: bsmith
> group: user
> folder: parsers
> title: html_parser
> integration stream: html_parser_int
> development streams:
> html_parser_int
> modifiable components:
> default rebase promotion level: INITIAL
> recommended baselines:
>
> 3. Remove the stream. The *–force* option bypasses the
> confirmation step.
>
> /cmd-context/ *rmstream -force html_parser_int*
> Removed stream "html_parser_int".
>
> 4. Reissue the *rmproject* command:
>
> /cmd-context/ *rmproject -force html_parser*
> Removed project "html_parser".
>
>
>
> On 4/24/07, *beginner* < mand...@gmail.com