Team development is a feature of JBuilder SE and Enterprise.
VSS and ClearCase integrations are features of JBuilder Enterprise.
Comparable terms
Checking out a file from the repository pulls the current repository version into your workspace. This keeps your workspace version up to date.
In some cases, checking a file out also means acquiring write access. Special privileges may be needed to use the command.
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.
Used from the context menu, this command is available only if it applies to all of the selected files. Available commands reflect what the version control status of all the selected files permits. For instance, with this command, all selected files must not already be checked out to you in order for you to apply the Check Out command.
This updates the selected files. Updating files retrieves changes from the repository and applies them to the files in your workspace.
When CVS updates, it automatically performs a merge, that is, it combines repository changes with your workspace changes. This synchronizes your workspace with the repository. All changes are preserved. If there are textual conflicts, they are flagged to be reconciled by the user.
Note that CVS only recognizes textual conflicts, not logical ones. A merge conflict happens when different users make changes to the same physical parts of the file. Updating frequently reduces the possible number of merge conflicts.
To learn how to reconcile merge conflicts, see the "CVS Update (Merge) File" topic in "Team development using JBuilder."
Checking out a file in Visual SourceSafe updates your work area with the latest version from the database and grants you write access until you check it in again. If somebody else has the file checked out, you can't write to it in your work area. You must have Check Out access to use this command.