Rule Builder > Working with Repositories in CVS > Managing Repository Elements with the CVS Plug-in > Committing Files to CVS |
Committing Files to CVS |
PREVIOUS NEXT |
Use the CVS Commit command when you want to incorporate changes from your working source files into the source repository. The commit command verifies that the selected files are up-to-date with respect to the current revisions in the source repository. It will notify you, and exit without committing, if any of the specified files must first be made current with update, see Updating Files From CVS. The commit command does not call the update command for you, but rather leaves that for you to do when the time is right.
The CVS Commit command can be carried out on any file or folder in the Project File Explorer that maps to a JRules package. You should always commit at the top-level.
To perform a CVS Commit on a selected file or folder and commit any modifications, additions, or removals to the JRules repository in CVS:
In the CVS Commit window, you are prompted to enter a log message. You can also choose to force the commit to a specified revision number or branch.
It is often useful to inform others when you commit a new revision of a file. There are a number of CVS features that can be used to automate this process.
Note |
Using the locking facility, if you set a project to read-write at the project level in the Project Explorer, the whole hierarchy below the project is put into edit mode. However, in the Project File Explorer with the CVS plug-in you must remember to commit all the files. If you use the CVS Commit on the top path, only that file will be committed. |
Updating Files From CVS | Editing Files in CVS
Customer Support | Copyright © 1987-2004 ILOG S.A. All rights reserved. Legal terms. | PREVIOUS NEXT |