02.05.2013 Views

User Guide - Mks.com

User Guide - Mks.com

User Guide - Mks.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 3: Getting Started Using Source Integrity<br />

Command Options<br />

58<br />

Resynchronize continued On Conflicts specifies the action to be taken when merge conflicts occur. Select one of<br />

the following options from the list:<br />

Confirm causes Source Integrity to confirm the action to be taken each time a<br />

conflict occurs.<br />

Cancel causes Source Integrity to cancel the operation when a conflict occurs.<br />

Mark For Later Merge causes Source Integrity to mark the files for merging at<br />

another time, allowing you to resolve the conflict first.<br />

Launch Tool causes Source Integrity to initiate the MKS Visual Merge tool.<br />

Highlight Output File causes Source Integrity to highlight conflicts in the<br />

resulting merged revision.<br />

Resynchronize Change<br />

Package<br />

Use Master causes Source Integrity to operate on the top-level sandbox. When the<br />

selected change package is associated with a member in a subsandbox, specifying<br />

Use Master causes the <strong>com</strong>mand to operate on the top-level sandbox for that<br />

subsandbox.<br />

Overwrite Working File if Changed overwrites the working file even if it has changed.<br />

Perform Merges prompts you for confirmation before performing a merge operation.<br />

Confirm Actions causes Source Integrity to confirm all operations with you before<br />

starting them.<br />

Verbose provides additional information to track the status of the <strong>com</strong>mand.<br />

Already in Project is Error causes Source Integrity to terminate the operation if the<br />

member being applied is already in the project. If this setting is negated (as in<br />

noAlreadyInProjectIsError), the information is displayed as a warning.<br />

Ignore Server in Change Package causes Source Integrity to perform the Resync CP<br />

operation even if the change package members reside on different servers.<br />

Span Projects applies the <strong>com</strong>mand to any member specified in the change package,<br />

even if this involves multiple projects. This option allows Source Integrity to search<br />

across local sandboxes for all entries in the selected change package(s).<br />

Ignore Cross-Branch Entries causes Source Integrity to use the most recent revision<br />

when it encounters two revisions of the same member on different branches.<br />

Restore Revision Timestamp sets the timestamp of the working file to the date and<br />

time of the last checked-in revision in the history. If this option is cleared, the working<br />

file’s timestamp is set to the current date and time. The time stamp is only changed if<br />

the working file is modified. If the resynchronize does not change the working file, its<br />

timestamp remains the same.<br />

Other Project is Error terminates the <strong>com</strong>mand if the member is not in the project you<br />

are applying to, or in its variant.<br />

Allow Open Change Packages allows Source Integrity to work with open change<br />

packages. This facilitates the application of a resolution change package.<br />

Create Variants causes Source Integrity to create new variant subprojects within the<br />

variant project as required to apply the change package members. If the main project<br />

contains required files that reside in a subproject, the Create Variants option creates<br />

variant subprojects for these files to be placed into.<br />

u s e r g u i d e

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!