Release Notes
5.4.16.739: Mar 30 2016
GitServer is out! The Plastic SCM server can now be configured to work as a Git server and attend push/pull operations directly from Git clients.
It means that you can use the Plastic SCM server as the central server for teams with mixed Plastic and Git users.
But even more important: GitServer works as a universal connector so that any Git compatible tool can now be connected to Plastic. Consider Continuous Integration software, code analysis, DevOps, and so on.
Learn more about GitServer here: https://plasticscm.com/gitserver/index.html
Issue trackers: Included support for multiples repositories for Polarion ALM issue tracker extension. Now it is possible to configure this feature by unchecking the 'Default Repository' checkbox from the 'Preferences' > 'Issue Trackers' dialog.
Issue trackers: Polarion ALM extension is now bundled with Linux (GTK) GUI.
Labels: Plastic SCM now allows label names to have slash ('/') characters.
Windows GUI: The 'Update operation report' dialog now shows workspace-relative paths instead of absolute paths.
Windows GUI: new 'Save as...' option in the 'Browse repository' window, so you can now save to disk file revisions while browsing a branch or changeset.
Proxy server: A whitelist feature has been implemented to automatically accept remote SSL certificates. To do so, create a file named plasticcached.trustedservers.conf in the proxy server binaries directory. Each line should contain a single hostname. Empty lines and lines starting with the '#' character will be ignored.
Example:
productionserver.mydomain.com pre.productionserver.mydomain.com #currently non-trusted servers: #dev.mydomain.com
Mergetool: New conflict resolution actions implemented for Linux, Mac and Windows mergetools:
* Keep source contributor & exit -> selects the complete source contents as the merge result.
* Keep base contributor & exit -> selects the complete base contents as the merge result.
* Keep destination contributor & exit -> selects the complete destinaion contents as the merge result.
In Windows mergetool, this feature is available in the 'Save & exit' button.
In Lunux and Mac mergetools, there is a new 'Merge' button in the toolbar to select the desired option, if any.
Linux (GTK) Mergetool: improved 'search' feature on diff and merge windows:
* Pressing Ctrl + F keys after selecting some text automatically fills the 'search' textbox with the selected text, and search matches are highlighted in the target contributor textbox in a single step.
* Pressing Enter navigates to the next match.
* Tooltips to the 'search' buttons added.
Mergetool: When merging file contents with no conflicts among them, the conflict resolution panel should not appear. Fixed.
Linux (GTK) Mergetool: diff window was unexpectedly increasing its size when opening a 'search' panel. Fixed.
Windows Mergetool: The 'Info about this merge' button was not correctly toggling the 'Info' panel, so it was not possible to close it once it was opened. Fixed.
Windows Mergetool: Non-default encodings were not properly detected in the 'Encoding' options menu. Fixed.
Mac OS Mergetool: 'Split conflict blocks' menu option fixed. The 'Result' panel was not updated with the expected contents after click on this option.
Mac OS Mergetool: Fixed an 'Index out of bounds' error when changing the file encoding to Unicode.
Command line client: The 'cm find mv' command was throwing a null exception when it was executed outside a workspace. Fixed.
Windows GUI: Diff window: The title of the 'Find in files' feature in the diff window was unreadable. Also, it was hard to distinguish the 'Find matches in ...' and 'Look in ...' menu options from the background. Fixed.
Windows GUI: The progress icon was not being shown in the default theme and 'Montana' themes in certain windows (such as 'Merge' or the 'Branch / changeset diff' window. Fixed.
Issue trackers in Linux (GTK) GUI and Mac OS GUI: Log checkin info to the issue tracker was not working in 'TaskOnBranch' mode (Bind issues to Plastic branches). Fixed.
Linux (GTK) GUI: Dynamic 'pending changes' view (from the 'items' view window): selecting a moved item caused the changed row for the same item (if exists) to be automatically selected also, which maybe is not the desired behavior for the user. Fixed.
Now, to submit a 'moved + contents changed' item, it is neccesary to select the item in both categories ('Moved' and 'Changed').