Working with projects under Rational Team Concert source control

Rational Team Concert™ source control uses an optimistic locking model that does not require a check out operation before you can modify files or folders. All files in a local workspace are normally writable. Modified files remain private to your repository workspace until you deliver them.
About this task

Rational Team Concert source control keeps track of the changes you make in your local workspace and displays them in the Pending Changes view. Each modified component in a workspace can include an Unresolved folder, an Outgoing folder, or both. These folders contain the changes you have made.

Changes you make to files and folders in your Eclipse workspace accumulate in the component's Unresolved folder until you check them in to a change set. (If you have selected the Auto check-in local changes preference, then the changes are automatically checked in to the component's current change set and appear in an Outgoing folder. For more information, see Choosing automatic or manual check-in.) Changes listed in an Unresolved folder remain private to your Eclipse workspace until you check them in.
Note: If you use external tools (ones that are not part of the Eclipse IDE) to modify files and folders, you typically need to refresh your workspace before Eclipse (and Rational Team Concert source control) can detect that modifications have been made. If resources you have modified are not visible in an Unresolved or Outgoing folder, navigate to the project in the Eclipse Navigator view (or any Eclipse view that lists the projects in your workspace), right-click it, and click Refresh. You can also refresh the project or any of its subfolders by clicking it and pressing the F5 key.

To check in your unresolved changes:

Expand the Unresolved folder to see the items it contains.

Feedback

Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug