export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:JazzInstallDir/jdk/jre/bin
before you start using scm subcommands, or embed the command in a shell startup script.[ -P | --password ]
indicates that you can type either -P or --password for this option. Optional options are delimited by braces. For example:scm load workspace [ -r
| --repository-uri ] repository URI or nickname
[ -d | --dir ] workspace-path { [ -q | --quiet ] [ -f | --force ] [ -c | --component ] name ... } component...
scm {options} {subcommand {subcommand options}}
When arguments to scm subcommand options contain spaces, they must be quoted. Shell wildcards are permitted where applicable (specifying files to check in, for example).
While many of the scm subcommands have options that support a one-time connection to a repository, it is generally more convenient to use the scm logincommand to store a repository URI and credentials, which can then be used by other scm commands. Credentials stored in this manner are difficult to discover. You can remove stored credentials with the scm logout command.
The scm load and scm share commands create a local workspace for use by Jazz source control command line tools. You can run Jazz source control command line tools in a local workspace or specify it using the -d option, which is common to all scm subcommands that require a local workspace context. If you are running the subcommand in a local workspace, you do not need to specify -d.
These subcommands do not allow you to specify a repository URI on the command line. Instead, they derive it from metadata associated with the local workspace in which you are running the command (or which you have specified using -d). If you have used scm login to store credentials for this repository, the subcommand does not prompt for them.
Do not use Jazz source control command line tools to work in an Eclipse workspace.
Many scm subcommands take an argument that refers to a repository object. These references can take the form of a name (such as the name of a workspace), a UUID ( a unique identifier assigned to each repository object), or an alias. Aliases are short strings of digits that you can use to refer to repository objects wherever such references are accepted by an scm subcommand. The scm command automatically creates these aliases whenever you run a subcommand that returns the name or UUID of a repository object. To use them, you must type the entire alias (they are not integers, so you must include leading zeroes when they are present). Aliases are unique to a workspace. You cannot share them with other team members. You cannot list them. They are not persistent over long spans of time (any alias can be reused to refer to another object after the set of unused aliases has been exhausted).
You can specify whether aliases, UUIDs, or both are displayed by setting the -a and -u options on the scm command line. (A value of y causes aliases or UUIDs to be displayed. A value of n causes them to be suppressed.
You can also show/hide aliases and UUIDs by passing -a yes/no and -u yes/no to scm. For example, scm -a y -u y list ws ... shows the alias/UUID of all workspaces. Substituting -a n shows just the UUIDs, and -a n -y n shows neither.
Examples presented in scm subcommand reference pages display and use aliases where appropriate.
| Flag | Status |
|---|---|
| @ | The change set is active. |
| ! | The incoming resource conflicts with the version of the resource in the workspace. |
| # | The incoming resource has a potential conflict with the resource in the workspace. |
| $ | The change set is closed. |
| a | The resource has been added. |
| c | The content or properties of a file have been modified, or the properties of a directory have changed. |
| d | The resource has been deleted. |
| m | The resource has been renamed or moved. |
C:\local-workspaces\HelloJazz> scm history .
(1009:) #@ nobody 32424 "degauss the flux capacitor" - "most recent changes"