Release Notes

Public

8.0.16.3799: Dec 02 2019

New

Windows - Plastic: Improved how we draw the selected comments in the new Code Review system.

Now, when you select a comment, the textbox draws a selection mark around the commented lines. Note that at the moment we only support single-line comments, but we'll support multi-line comments soon.

New

Command line client: we improved the warning message when an operation can't run because another operation already locked the workspace - it now tells you which operation is locking the workspace.

This is the old message:

The object is currently locked. Try later. Workspace: 'test_wk'.

And this is the new one:

An existing merge operation has locked the workspace 'test_wk'. Please wait for the merge operation to finish.

New

Windows - Gluon: Incoming changes: the new 'Incoming changes" view is now complete, so it allows you to preview, download and solve file conflicts when there are new changes.

This feature is experimental. You need to manually activate it by adding the following line to the client.conf configuration file.

On Windows, it is at %LocalAppData%\plastic4 folder:

<EnableGluonIncomingChanges>yes</EnableGluonIncomingChanges>

Current limitation:

* There is no notification saying there are new changes available yet.

New

All platforms - Server: We added some new extensions to the default lock rules. We also tweaked a little bit the WebAdmin's Lock Rules webpage to better explain how global lock rules apply to repositories.

New

Windows - Plastic: Did you notice that you couldn't display the contents of added/deleted items in a merge preview? Well, this update will put that inconvenience in your rearview mirror. You'll notice that the "Diff ancestor with source contributor" item is now enabled in the merge view for those added/deleted source conflicts. Clicking them will display the revision contents in a new window.

This applies to the Incoming Changes view, too. The menu item title changes: it's "Diff incoming changes" instead.

New

Windows - Plastic: Some customers asked for a way to show the old code review window when opening a code review. This is now possible by adding a --oldcodereview argument to the Plastic GUI application:

plastic.exe --oldcodereview

Bug

Windows - Gluon: The History and Undelete panel tables didn't have the appropriate styles applied to them. Fixed!

Bug

All platforms - Client: We fixed the error "Can't add an entry with the same name" that could happen in operations that apply local changes. That might be the checkin, undo changes, or explicitly apply the local changes (convert local uncontrolled changes in checkouts).

The issue happened when you locally moved a directory with one of their children checked out, and you locally moved another controlled file in the new destination of that checked out file.

Let's see an example. Add the following structure, each file having different contents:

/dirA
/dirA/file1.txt
/dirA/file2.txt
/dirA/file3.txt
/dirA/file4.txt
/dirA/file5.txt
/dirA/file6.txt
/file.txt

Now, checkout file /dirA/file3.txt:

co /dirA/file3.txt

Then, rename dirA to dirB outside Plastic. If you're using the Windows command prompt, this is what you'd type:

move dirA dirB

After that, take the controlled file /file.txt and move it (using the shell or Explorer, not Plastic) to overwrite /dirB/file3.txt (which used to be /dirA/file3.txt and is checked out):

move /Y file.txt dirB/file3.txt

Finally, run a global undo operation:

cm unco --all 

At this point, the command above failed with the mentioned error "Can't add an entry with the same name".

Please note that this issue happened while the command tried to apply the local changes to convert them to controlled ones. So, the same thing could happen if you right-clicked these changes in the Pending Changes view and clicked "Checkout" in the popup menu.