This command is used to synchronize an Eclipse workspace with a sandbox that was loaded with the Rational Team Concert scmtools commands or a Rational Team Concert build.
A sandbox is a hierarchy of directories and files that do not constitute an Eclipse workspace. Rational Programming Patterns therefore cannot use the sandbox directly.
With this command, you can use the sandbox by synchronizing the changes that it contains with the workspace.
You can run this command during a Rational Team Concert build. In this case, the sandbox that was loaded during the build is used.
With this command, you can also export the files that have been updated in the local workspace since the synchronize command was last run. These files have an XML format. They contain the update type (creation, modification, deletion) and the updated design file or COBOl source file.
Options | Comments | Required | Default values |
---|---|---|---|
--sandbox | Full path to the sandbox. It must contain a consistent set of projects from which a Rational Programming Patterns location can be created. It must be different from the Eclipse directory that is indicated in the --data option. |
Yes | No default value |
--data | Full path to the workspace | Yes | No default value |
--log | Log file name | No | trace.log |
--notificationHandler | Parameter that indicates that the synchronization
command must migrate the notifications with the specified notification
handler. The xmlExport handler is provided. |
No | No default value |
--initialNotification | Initial notification for the sandbox. The notifications for all the elements that are taken into account have a created status. |
No | No default value |
--handlerConfiguration | Configuration properties for the specified notification
handler. You indicate the output directory of the XML files with the xmlExportDir key. |
No | No default value |