After switching from offline to online mode, you cannot submit changes in the Synchronize view while the MKS status cache refreshes. Before you submit changes, check the status of the Eclipse progress bar and ensure there is no MKS command activity.
You cannot submit changes in the Synchronize view while Eclipse refreshes. Before you submit changes, view the status of the Eclipse progress bar.
When a subproject is dropped in another user’s Sandbox, resynchronizing the dropped subproject’s members in the Synchronize view displays an error message. To avoid this, resynchronize the dropped subproject in the Package Explorer.
The Synchronize view updates if you change the active change package from <none> to a change package, or from one change package to another change package; however, the
Existing locks on dropped members are not removed. To resolve this, open the Locks view in the MKS Integrity Client GUI and unlock the members.
Performing the View Sandbox command on a dropped subproject incorrectly displays an error message.
In offline mode, you cannot refactor (rename/move) a file that is not under MKS version control, but exists in an Eclipse project under MKS version control.
Moving and then renaming a member incorrectly displays it as a new member. Consequently, this causes the integration to create a new member archive when you submit your changes.
If you delete a subproject in offline mode, the Sandbox icon is removed from the subproject. In offline mode, MKS recommends that you do not perform MKS Integrity commands that affect the repository, such as deleting or renaming resources.
The initial attempt to rename a subproject after adding a member to the subproject displays the error message “the Resource is out of sync with the filesystem.” Refreshing the subproject, then performing the rename command successfully completes the operation.
Attempts to revert deferred added members from the Synchronize view do not successfully remove them from the Synchronize or Packages views. Reverting the files from the MKS Integrity Client successfully removes them from both views.
Initial attempts to rename Java packages or add linked files to Eclipse projects under MKS version control fail; however, subsequent attempts are successful. These are known Eclipse 3.3.1 issues.
If you deselect the Use active Change Package option in Preferences > Team >
MKS Source, Eclipse incorrectly allows you to filter the Synchronize view by the active change package.
If you select a file in Eclipse 3.3.1’s Synchronize view that you know contains modifications and double click it or select Open in Compare Editor from the shortcut menu, Eclipse may incorrectly state that the entire file is different. To avoid this error, select Window > Preferences > General > Compare/Patch > Ignore Whitespace.
IBM Rational Software Development Platform products do not dynamically update subprojects in the MKS Integrity Client GUI if you use the Configure Subproject command in MKS Integrity. To update these subprojects, restart Eclipse, and resynchronize the subprojects in the MKS Integrity Client.
To avoid potential focus problems when using the MKS Sharing Wizard, close the MKS Integrity Client if it is open.
To hide files, such as the MKS Integrity project registry file (project.pj), certain resource filters are enabled by default in Eclipse. By default, these filters apply to the Packages and Navigator views. In Eclipse 3.3.1, filters in the Navigator view do not work.
When using change packages in the MKS Integrity integration with Eclipse, it is important to note that the Submit Changes command in Eclipse does not perform the same function as submitting a change package through the MKS Integrity Client GUI. Using Submit Changes in Eclipse means that pending revisions are checked in; however, when Eclipse prompts you to commit those changes and you choose No, those changes can no longer be committed from within Eclipse unless you have additional changes to submit. In addition, while working in the Eclipse environment, you cannot submit that change package or determine whether the change package has been processed. In this situation you can continue to work, submit your next set of changes, and then choose Yes to close the change package and complete the submission. In the alternative, if you do not have additional changes to submit, you can submit the change package using the MKS Integrity Client graphical user interface.
There are a number of conditions that may cause Eclipse to identify new files in a project, resulting in deferred add operations for non-member files that have not been modified by the user within the Eclipse IDE. For example, in cases where automatic refresh is enabled in Eclipse and files are generated by build scripts, the generated files are identified by MKS Integrity as new files to be added to the project.
If you routinely encounter this situation and do not want MKS Integrity to add such generated files to your projects, you can add the file type to the Eclipse Ignored Resources list. Under Window > Preferences > Team > Ignored Resources, add the pattern for the file type you want the integration to ignore.