Who we are

We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

If you want to give it a try, download it from here.

We also code SemanticMerge, and the gmaster Git client.

Plastic SCM is out!!

Monday, October 01, 2012 Amalia 0 Comments

A new release of the 4.1 version is out: Plastic SCM has been released.

All the new features and bug fixes of each Plastic SCM release can be found in the release notes page

Besides the full release notes, this blogpost will highlight some of them. Just in case you haven't downloaded this version yet you can do it here.


Database Integrity

There's a new command in the CLI: checkdatabase.

This command checks the database integrity of a Plastic SCM repository.


"cm checkdatabase [spec]".

The "spec" argument is a repository specification it could be a server or repository (rep:default@localhost:8084)

Remarks: If the [spec] parameter is not specified, the checkdatabase command will use the default property defined inside the "client.conf" file.


  • cm checkdatabase repserver:localhost:8084
  • cm checkdatabase rep:default@localhost:8084

Integrate Atmel Studio 6 with Plastic SCM

Added support for Atmel Studio 6.0 in the installer. This IDE is base on Visual Studio 2010. The package will be installed in Atmel Studio by means of the VSIX installer used for Visual Studio 2012.


Export View Data in History View

An error occurred processing your export view data in history view, the file to export is created, but no data is exported.

Fixed!! The problem was caused by the Labels column. If this column had null values, an exception was caused when trying to get the string from the object. The Labels column has been removed. It's no longer necessary.

Move changes dependencies to CLI

When a full checkin was done from the CLI using the option "--applychanged", only the changed items under the current directory were committed instead of applying all the workspace changed items. Fixed!!

Enjoy it!!

0 comentarios: