Login

Although the scm command supports persistent login using the scm login command, it is not used by this provider. The username and password can either come from the URL in the pom.xml file, or from a <server> section in a settings.xml file. The password is masked in the output of the execution of the scm command.

Note Having the username and password set in the pom.xml takes precedence over the <server> entry from settings.xml.

Add

Jazz SCM does not have the equivalent of an add command. This implementation uses the scm checkin command. However, it does not call the scm deliver command, nor does it create a changeset.

Blame

This provider uses the scm annotate command.

Branch

Not implemented.

A branch in Jazz SCM is roughly equivalent to a Stream or possibly even a Repository Workspace, depending on how the flow targets have been defined, thus the branch command could be used to create a new Stream or Repository Workspace. The Jazz SCM command scm create workspace can be used to create new Repository Workspaces, however, there is currently no scm create stream command.

Jazz SCM also further complicates the issue by allowing multiple flow targets.

This provider does not currently explicitly support multiple flow targets. When there are multiple flow targets defined, the flow target defined as "current" will be used, not the "default" one. This information is obtained from the output of the scm status command.

Note Some commands, such as edit and unedit work with the implicit flow targets of the Repository Workspace.

Changelog

This provider uses the scm history command to obtain a list of all changesets. It then uses the scm list changesets to obtain the details of each individual changeset.

Checkin

This provider will create a changeset with the provided message. The implementation uses the scm checkin command, it uses the Add command implementation.

If the repository workspace has a valid flow target (ie, not itself) and the pushChanges option it true, which by default it is, then this provider will also deliver the changes to the flow target using the scm deliver command.

Note: Only a single flow target is currently supported. When multiple flow targets have been defined, the flow target marked as "current" will be used. This provider is not aware of the other targets. This information is not available from the scm status command.

Checkout

The implementation uses the scm load command.

Diff

The diff implementation produces a diff based on the difference between changes in the sandbox and the repository workspace. A flow target, if defined, is not used. The scm command is not currently able to produce a single diff output of all files that have changed. So the scm status command is used to determine all changed files, and then iterates through the list, calling scm diff for each individual file.

By default, an ${artifactId}.diff file will be produced in the current working directory. This .diff file can be then imported into the Eclipse Client using the following procedure.

Right click, then, Team > Apply Patch...

In the dialog that opened, select the patch file. Note that no files will be shown in the 'This patch effects the following files' list. Select Next. Choose the 'Workspace Root' radio button and then click on the Finish button.

In the 'Pending Changes' view, select 'Merge into Workspace'. The patch will be applied.

Edit

The implementation uses the scm lock acquire command, and uses the implicit flow targets defined for the repository workspace. If none are defined, the command will fail.

List

The scm status command is called first to obtain the remote repository workspace and component name. These are then used as parameters for the scm list remotefiles command.

Status

This provider uses the scm status command.

Tag

The scm status command is called first to obtain the remote repository workspace and stream name. The Jazz SCM equivalent of a tag is a snapshot. A baseline could have been used, however, baselines are not supported or used by this provider. Please note however, that when a snapshot is created, a baseline will also be implicitly created. Also, Jazz SCM currently does not support the loading of a snapshot directly, we can only load from a repository workspace. So, to facilitate this, the tag command also creates a remote workspace repository of the same name as the tag, ie: ${artifactId}-${version}.

This provider can call up to four different scm commands to fully accomplish this function.

• The scm create snapshot command is first called to create snapshot.
• The scm create workspace command is called to create a repository workspace that can later be loaded by the checkout command (for the release plugin).
• The scm deliver command is called to deliver the changes to the flow target (if defined and pushChanges is true).
• The scm snapshot promote command is called to promote the snapshot to the flow target (if defined and pushChanges is true).

Unedit

The implementation uses the scm lock release command, and uses the implicit flow targets defined for the repository workspace. If none are defined, the command will fail.

Update

This provider uses the scm accept command to receive updates into the remote repository workspace. If a sandbox has been loaded from the remote repository workspace, it too will also be updated.