Release Notes
11.0.16.9243: Mar 06 2025
Windows - Installers: Simplified install cycle with less steps
* Removed redundant "Start Classic GUI or Gluon" question, since the first startup after a fresh install already asks for this choice.
* Removed component selection window, since it allowed the installation of the Eclipse plugin, which is still possible by copying the bundled plugins .jar files located at $INSTALL_DIR/client/plugins/eclipse directory.
A "README.txt" file can be found in that directory with installation instructions.
Besides that, the "More installers and other Operating Systems" section of https://www.plasticscm.com/download enables downloading a "Plugins zip" file containing all java-based plugins, including eclipse plugin.
All platforms - Command-line client: Incoming Changes support for 'cm partial update' command
A new '--incoming' option has been added to the 'cm partial update' command, aligning its behavior with Gluon. This enhancement scans for local workspace changes and applies only those relevant to the operation. Additionally, it will attempt to automatically merge any file conflicts it encounters.
All platforms - Command-line client: Fixed issue when running merge-to outside of a workspace
When trying to run a merge-to operation while the current working directory is not inside a workspace, we were showing an error. Now you can successfully complete the merge-to from any location.
All platforms - Gluon: Check-in failure when reverting a directory with moved items
Fixed an issue where Gluon failed to check in a directory revert operation if any item had been moved between the workspace revision and the reverted revision. The operation would throw the error: "An item with the same key has already been added." This issue has now been resolved.
All platforms - Gluon: Fixed checkin success message
After performing a checkin in Gluon, we show a notification at the bottom telling that the operation was completed successfully. This message was notifying of a successful shelve operation, instead of a checkin. We fixed the text of the notification.
All clients: Incoming Changes may incorrectly flag files as modified despite no actual changes
After resolving a file conflict, the Incoming Changes operation did not update the file's local information. As a result, the file may incorrectly appear as "changed" even when no modifications were made, and this issue could persist even after checking the file in. Fixed.