The following advanced MKS Integrity commands are available from the MKS menu and/or Team shortcut menu:
Command Function
Lock Equivalent to the MKS Integrity Lock command.
Right-click the selected file in the Package Explorer or Project Explorer view, and select Lock.
Move to Change Package Moves the selected files to an existing or new change package. The change package containing the associated changes can then be submitted to the MKS repository.
IMPORTANT: Moved or renamed files cannot be moved to a new change package in Eclipse. Move these files to a new change package in the MKS Integrity Client.
From the list, select a change package or click Create Change Package.
Submit Changes Equivalent to the MKS Integrity Submit command. Submits uncommitted changes on individual files.
If the changes are part of a transactional change package, then the change package entries are left in a pending state.
If there are outgoing changes that are not in change packages, you are prompted to associate the changes with the active change package.
If you click Yes, the outgoing changes are associated with the active change package. If no active change package exists, the integration attempts to submit the changes in the :none
change package.
If you click No, the integration submits the outgoing changes without a change package. If your server policy specifies that change packages are mandatory, an error displays.
If you click Cancel, the submit operation is cancelled. The status bar indicates when the command is complete. NOTE: If the selection is from the Packages view, a submit does not include dropped files; however, a submit includes dropped files displayed in the Synchronize view.
Resynchronize Equivalent to the MKS Integrity Resynchronize command. Gets the latest version of the selected file and puts it in your working directory.
The Overwrite dialog box may display.
The status bar indicates when the command is complete.
Resynchronize by Change Package
Equivalent to the MKS Integrity Resynchronize Member by Change Package command.
Processes the change packages associated with the member you are resynchronizing, and brings the changes from the project to your Sandbox.
Depending on the preferences you have set for the Resynchronize command, the Confirm Overwrite Working File dialog box displays.
Revert Equivalent to the MKS Integrity Revert command.
Replaces the working file with the revision that was checked out, as it appeared prior to modification, and unlocks the file (and removes it from the associated change package).
NOTE: You can revert a file in a change package that is not the active change package. Reverting the file removes it from the change package.
The Overwrite dialog box may display.
The status bar indicates when the command is complete.
View Member Differences Equivalent to the MKS Integrity Differences command. Compares the selected working file with the member revision. Visual Difference automatically launches and displays the two
View Member History Equivalent to the MKS Integrity View Member History command. Displays the revision history of the selected file.
The Member History view displays.
View Annotated Revision Equivalent to the MKS Integrity View Annotated command. Displays the annotated revision history of the selected file. The Annotated Revision view displays.
Create Change Package Equivalent to the MKS Integrity Create Change Package command.
Creates a change package.
The Create Change Package dialog box displays.
View Active Change Package Equivalent to the MKS Integrity View Change Package command. Displays the active change package associated with the selected file. If there is no active change package, this command is disabled.
The Change Package view displays.
For more information on active change packages, see “Working With Active Change Packages” on page 43.
Resynchronize Change Packages
Equivalent to the MKS Integrity Resynchronize Change Package command.
Previews the changes listed in change packages in the context of a Sandbox before propagating them to the project.
The Resynchronize Change Packages dialog box displays. After you resynchronize the change package containing the changes, the changes appear as operations not yet committed to the MKS repository.
Once you are satisfied with the changes and want to commit them to the MKS repository, submit the change package, and then resynchronize the members.
IMPORTANT: After resynchronizing by change package, the changes may appear as incoming changes in the Synchronize view. Do not resynchronize the changes; otherwise, they will be lost. Update the revisions by submitting the changes.
For more information on submitting changes, see “Team Synchronizing” on page 54.
Submit Active Change Package The Submit Active Change Package command allows you to submit an active change package directly from the MKS menu within Eclipse.
The Submit Active Change Package command operates in the same way as the Submit Change Package command on the MKS Integrity Client, and follows the client preferences as set for
Create Subproject Equivalent to the MKS Integrity Create Subproject command. Creates a subproject in the selected directory and adds it to the MKS Integrity project.
After you type a name for the subproject, the Create Subproject dialog box displays.
NOTE: If a conflict or error occurs when attempting to name the subproject, the name entry dialog box displays, prompting you to type a new name for the subproject.
Convert to Subproject Converts an empty directory or a directory containing files that are not under MKS version control to a subproject. If the directory contains files, they must be added to MKS version control after the subproject is created.
This command is useful for defining a directory structure for a build project.
Drop Subproject Equivalent to the MKS Integrity Drop Subproject command. Drops the selected subproject(s) from the MKS Integrity project, deleting all files and directories under the subproject(s). The Drop Subproject dialog box displays.
View Sandbox Equivalent to the MKS Integrity Open Sandbox command. Displays a Sandbox view.
View Project Differences Equivalent to the MKS Integrity Project Differences command. Displays the differences between project checkpoints. The Project Differences view displays.
Checkpoint Equivalent to the MKS Integrity Checkpoint command. Checkpoints one or more Eclipse projects under MKS version control. If the project is a subproject, the checkpoint recursively checkpoints everything under it; parent projects in the hierarchy are not checkpointed.
Adialog box displays, prompting you to choose one or more Eclipse projects, and to, optionally, add a label and description. NOTE: Labels are applied to the Eclipse project, but not project members.
A confirmation dialog box indicates which projects were successfully or unsuccessfully checkpointed. A maximum of 15 projects appear in the confirmation dialog box.
Work Offline/Online Toggles offline/online mode.
For more information, see “Online and Offline Mode” on page 32.
Open MKS Client Equivalent to launching the MKS Integrity Client GUI. TIP: You can also launch the MKS Integrity Client by clicking in the MKS trim.
Note the following:
You can make the MKS menu always available from the perspective you have open by selecting Window > Customize Perspective. In the Commands panel, enable MKS Source Menu.
In Eclipse version 3.3 or greater, you can use Eclipse’s key binding functionality to assign key sequences to commands in the MKS and Team menus. Note that MKS commands are only visible when Include unbound commands is enabled on the Preference > Keys page. (This option to assign key sequences is not available in Eclipse 3.2.) For more
information, refer to the Eclipse documentation.
Although Eclipse supports linked resources, known as out-of-tree members in MKS Integrity, they cannot be placed under MKS version control. As a result, MKS commands are disabled and decorators do not appear when you select linked resources. If you select one or more files and then perform a revert or resynchronize, only the
selected files are reverted or resynchronized. If you select one or more containers (Eclipse projects, directories, packages) and then perform a revert or resynchronize, the integration examines the first Sandbox or subsandbox of each container and performs a revert or resynchronize on the entire Sandbox or subsandbox. If you select an Eclipse container that maps to a directory in MKS Integrity, the Sandbox containing the directory is resynchronized or reverted.