Comparable terms
Checking a file into the repository applies the changes you made locally to the version of the file that resides in the repository. This allows the version control system to log and track the changes that you make, and keeps other users up to date on the file's evolution.
This command is available from the Team menu for the file that's active in the content pane, and from the context menu in the project pane for all selected files.
This feature is supported in the CVS, Visual SourceSafe, and ClearCase integrations.
For a glossary of generic version control terms, please see the Version handling glossary in "Comparing files and versions" in Building Applications with JBuilder.
Update your files before you commit them. This reduces merge conflicts and, where conflicts happen anyway, engages JBuilder's conflict assistance mechanisms.
Select this command either from the Team menu or from the context menu. The CVS Commit dialog box will appear. If you're committing one file,
If you're committing multiple files, you will be prompted for a comment as before. You will also be shown a list of the selected files.
Select this command either from the Team menu or from the context menu. The Check In Files dialog box will appear. If you're checking in one file,
If you're checking in multiple files, you will be prompted for a comment as before. You will also be shown a list of the selected files.
If a user checks out a file and checks it back in without making any changes, VSS automatically performs an Undo Checkout in order to prevent creating an extraneous version of that file.
Select the Check In command from either the Team menu or from the project pane context menu. The ClearCase Check In dialog box appears. It lists the files you elected and prompts for a summary description of the changes to the files. It gives you the option of keeping the files checked out after they are checked in.
When Check In is used, JBuilder looks for updates to the selected files before checking them in. If any of the files have been changed by others, they are displayed in the Merging Files dialog box.
Click OK to allow JBuilder to merge the files. This is normally straightforward and results in a single version of each file that incorporates the revision on the repository with changes that you made locally. If there are differences in exactly the same physical part of the text, this will register as a conflict. JBuilder displays files with conflicts in another dialog box, and does not check them in. Unconflicting files will be checked in as usual.
Note: Conflicts must be resolved in ClearCase.
Click Cancel if you don't want to merge these files and risk a conflict. They will be removed from the list of files to be checked in at this time. The other files will be checked in normally.