Synchronizing a local workspace

When all local changes are checked in, your local and repository workspaces normally have identical content. Network failures or cancelled operations can sometimes lead to differences in this content. In many cases, you can resolve these differences by re-loading the workspace. If the workspace contains changes that you have not checked in, save them as a patch because they will be overwritten by the re-load.
About this task

Local and repository workspaces can become out of sync when a network failure or user cancel interrupts an operation that updates both workspaces. When this happens, the next attempt to perform an operation (such as check-in, accept, suspend, or resume) that updates both workspaces generates a warning that the workspaces are out of sync and displays a window that lists the out-of-sync projects and prompts you to select projects to overwrite when the workspace is re-loaded.

If any of the out-of-sync projects contains unresolved local changes, the re-load overwrites them. To preserve these changes, create a patch that includes them, and then apply it after the re-load completes. For more information, see Creating and applying a Rational Team Concert source control patch.

If you cannot create a patch, you can disconnect the affected project from Rational Team Concert source control and then share it again. This operation compares the contents of the Eclipse and repository workspaces and expresses the differences in one or more changes that, when checked in, synchronize the two workspaces. Review the changes and undo any that you do not want to check in.


Feedback

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