Jump to content

3.0.187.25 is out BL187.25


miller

Recommended Posts

Another two releases full with improvements, new integration "Bamboo Plugin" and bug fixes, go download the Plastic SCM 3.0.187.25.

Download page: https://www.plasticscm.com/download/

Release Notes:

External Release 3.0.187.25 (May 27th 2011)

===============================================

New

Merge: Included an option to filter contributors without changes in

a merge operation (conflict contributor is "None"). This is optional and

by default it is not set. Once the option is set on a merge it will be

saved as default.

Bug

Small typos fixed in several error messages. Fixed.

External Release 3.0.187.24 (May 20th 2011)

===============================================

New

Bamboo plugin: Plastic SCM now includes a plugin to work with the

Atlassian Bamboo continuous integration application.

New

Eclipse plugin: A checkbox has been added to include changed items

on the sync view and the commit dialog.

Bug

Compatibility check between client and server was not correctly handled

when the authentication mode was LDAP. Fixed: now the client checks the

compatibility and shows an appropriate message, explaining the client

version of the commontypes library and the server version of that

library.

Bug

Branch Explorer: The statistics chart did not show the expected days

(the same as the Branch Explorer was showing) for the daily number of

checkins. The problem was that the data was not sorted correctly. Fixed.

Bug

Code review: There was a bug when trying to add a note in a recently

added item. Fixed.

Bug

Visual Studio Package: The offline checkouts were not restored when

Visual Studio was restarted. Fixed.

Bug

Visual Studio Package: The Plastic SCM context menu should be disabled

for unbinded items. Fixed.

Bug

Proxy installer: problem solved related to a library not included in

the installer. Fixed.

Bug

The sbb command returned a null pointer when it was executed out of a

workspace. Fixed: now it shows a correct message.

Bug

LDAP authentication: sometimes it could not get a response when getting

users. Fixed: this happened because sometimes the calls were not

correctly processed and they did not return the control, so the thread

kept busy.

Enjoy!

Codice Software Staff

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...