Working with projects under Jazz source control

Jazz™ 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.

Jazz 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 Jazz 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.

To check in the entire set of unresolved changes to the current change set, right-click the Unresolved folder and click Check-in all.
To check in an individual item in the Unresolved folder, right-click it, click Check-in, and click an existing change set to receive the change, or click New change set to create a new change set. (A file or folder in a component cannot be part of more than one active change set. When a file or folder is included in an active change set, all changes to it become part of that change set whether or not the change set is current, and changes to that file or folder cannot be explicitly checked in to a new change set until the active change set that includes it is completed.)

Selecting resources to exclude from Jazz source control
Eclipse workspaces often include files or folders, such as compiler output, log files, and so on, that you do not want to place under source control. You can specify resources or classes of resources to be ignored by Jazz source control. Ignored resources are never checked in.
Specifying file properties and line delimiter types
Jazz source control includes a File Properties preference page on which you can associate a MIME content type and line delimiter type with a file name suffix. Review these mappings and modify them as needed before you share a project to Jazz source control
Choosing automatic or manual check-in
The default behavior of Jazz source control requires you to check-in your work manually. You can change this behavior if you want to check in your work automatically when you save a file, or based on other criteria.
Viewing files in the repository
Use the Repository Files view to browse the files in a repository workspace or stream.
Searching for repository objects
Jazz source control search can search the repository for objects such as change sets, snapshots, components, repository workspaces, or streams.
Creating and managing change sets
Checking in any file or folder in a component adds it to the component's current change set and copies the change to your repository workspace. By default, all changes to a component accumulate in its current change set. You can create new change sets, designate one of them current, move items from one change set to another, and remove change sets temporarily or permanently from your workspace.
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.
Creating and applying a Jazz source control patch
A Jazz source control patch is a file that captures the differences between a project in a local workspace and its counterpart in the repository.

Feedback

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