Release Notes
Public
11.0.16.7739: Jan 26 2023
~ WARNING ~
In a clean macOS machine, the server-side merge operation won't find the merge tool if there are text file conflicts. This happens due to a configuration issue.
As a workaround, you need to edit the text-based merge tool through the 'Preferences view' > 'Merge tools' tab in order to use '/usr/local/bin/plasticgui xmerge' (instead of 'plasticgui merge').
New
All Platforms - Gluon/GluonX: Incoming Changes only checks-out local changes involved in conflicts.
Before, the Incoming Changes applied all the local changes in the workspace before running the operation. It didn't matter whether these local changes were in conflict with the changes to update/merge or not.
This could end up locking exclusively some files that were only locally modified (unrelated to update operation) and preventing other users to modify those files due to an undesired lock.
Now, only the local changes that are in conflict with the server changes to update/merge are applied in the workspace.
New
Command-line client: Partial update command improved for automation
Several adjustments have been made to the partial update command:
* There was no --xml option in the partial update command. Now it is available.
* --xml option can be used in a pipeline.
* Using the --xml option implies --silent. Informative output gets trimmed.
* Using the --silent option removes informative output only. Warning and error messages are still written through standard error output. You can silence those messages by using output redirection.
New
All platforms - Plastic: Diff images available for binmerge tool
Now you can specify two arguments to the "plasticgui binmerge" command, the source and the destination contributors, to diff them instead of performing a merge. Both files must be images:
plasticgui binmerge -s=source.png -d=destination.png
New
All Platforms - Plastic: SemanticMerge match/unmatch
Ported match/unmatch functionality to new GUI for SemanticMerge.
Bug
All platforms - Plastic: Fixed issue applying directory conflict resolutions from shelveset
When applying the changes in a shelveset you can choose which of the changes you wish to apply. There was a bug which meant that if you chose to apply only resolved directory conflicts you would be told that no changes were selected and you would not be able to apply those changes. We fixed this, so now you can apply your directory conflict resolutions without issue.
Bug
All platforms - Plastic: App hang on closing if Pending Changes View is refresing
Plastic didn't respond if the user closed the GUI or switched to another Workspace when Pending Changes View was running a "finding changes in the workspace" operation.
This issue is now fixed.