Community
Participate
Working Groups
Some CVS users are used to using the release command to delete their working checkout (e.g. in Eclipse terminology this means to delete the working project). In Eclipse you can workaround this: 1. release the project 2. delete project from workspace (simply by deleting from within Eclipse) Note: this won't trigger a note added to the cvs history file. Cancels a checkout (indicates that a working copy is no longer in use). Unlike most CVS commands that operate on a working copy, this one is not invoked from within the working copy but from directly above it (in its parent directory). You either have to set your CVSROOT environment variable or use the -d global option, as CVS will not be able to find out the repository from the working copy. Using release is never necessary. Because CVS doesn't normally do locking, you can just remove your working copy. However, if you have uncommitted changes in your working copy or you want your cessation of work to be noted in the CVSROOT/history file (see the history command), you should use release. CVS first checks for any uncommitted changes; if there are any, it warns you and prompts for continuation. Once the working copy is actually released, that fact is recorded in the repository's CVSROOT/history file. NOTES:
Should be considered in 2.0 CVS provider.
PRODUCT VERSION: 0.037 JT
This is related to watch/edit. We should consider for 3.0
Reopening
We should provide the user with a preference to perform a "cvs release" when a project is deleted. We can then check this preference in the move/delete hook and take appropriate action.
This bug has not been touched in 2 years. Closing as WONTFIX.
New Gerrit change created: https://git.eclipse.org/r/c/papyrus/org.eclipse.papyrus-sirius/+/200653
Gerrit change https://git.eclipse.org/r/c/papyrus/org.eclipse.papyrus-sirius/+/200653 was merged to [bugs/protoSiriusWithEEF]. Commit: http://git.eclipse.org/c/papyrus/org.eclipse.papyrus-sirius.git/commit/?id=3da8dd5c8d8d50c06af8f0d02a2b47661c0bfc55