Release Notes

Update operation: The update operation was raising an "Access to the path is denied" error when updatig hidden files on Windows OS's.

Unity users with VCS mode = "Hidden meta files" experimented this issue. Fixed.

Maven: The Maven 'tag' command was failing on Linux systems when calculating the items that were tagged. Fixed.

Merge: The recursive merge operation generates virtual revision identifiers to resolve the conflicts between the multiple common ancestors.

These identifiers could be used to track delete operations in the extended merge item information, but they cannot be used in the merge result, as they are temporary identifiers and not real revision identifiers. This issue has been fixed and now the real revision identifiers are used.

Command line client: The diff command for changesets was not correctly using the repository spec inside the fully-qualified changeset spec (Example: cs:529@tools@server:8087).

It was only considering the repository of the working path. Fixed. Now, the repository will be taken from fully-qualified changeset spec.

GUI: showing differences from the pending changes view was not setting the configured comparison method to launch the diff tool. Fixed for both the embedded diff viewer and external diff viewer (Ctrl+D).

Replication: unable to replicate new changes in the following scenario:

* An empty branch was replicated

* Later new changesets were checked in both in the source

and destination repositories

* The new replication was unable to replicate new checkins

Scenario to reproduce the issue:

* Create an empty branch task001.

* Replicate task001 from repo A to repo B.

* Create a changeset on task001@repository A.

* Create a changeset on task001@repository B.

* Replicate (pull) the branch -> Nothing is replicated (Now it's fixed).

Replication: problem updating the 'head' of a branch. It happened under the following circumstances:

* A branch was replicated again from source to destination

* If the new head or some changesets between the old head

and the new head were replicated on different replication

operations.

Note: the issue only happened if empty branches were replicated.

Fixed.

Scenario to reproduce the issue:

* Create two changesets on main branch.

* Create an empty branch from the last changeset (main head).

* Replicate the empty branch.

* Replicate the main branch -> The main head was not updated

properly (Now it's fixed).