This page has been archived and is no longer updated.

To buy this product, please visit: http://www.plasticscm.com

Plastic SCM Standard

A complete SCM (Software Configuration Management) solution with Eclipse and Visual Studio integration.

Published by Codice Software
Distributed by ComponentSource since 2015

About Plastic SCM Standard

A complete SCM (Software Configuration Management) solution with Eclipse and Visual Studio integration.

Plastic SCM Standard Edition is a source code version control system with full integration with Visual Studio and Eclipse IDEs, and with accurate importers for SourceSafe and CVS, providing quick transition from these environments. Plastic SCM Standard is the entry level editiond and provides support for up to 10 developers. Plastic SCM Professional Edition provides support for unlimited users, enterprise features such as configurable workspaces through selectors, integration with Active Directory or linux support.

Plastic SCM Standard Edition is a source code version control system with full integration with Visual Studio and Eclipse IDEs, and with accurate importers for SourceSafe and CVS, providing quick transition from these environments. Plastic SCM Standard Edition support all core version control functionality found on Plastic SCM Professional Edition, however, it will suit a small team of up to 10 developers. For unlimited user support, advanced security features, Branch Explorer, Multiplatform support etc, please, refer to Plastic SCM Professional Edition or visit the 'evals and downloads' section of this product page for the complete feature comparison between both Plastic SCM editions.

Plastic SCM Standard Edition Features:

3D Version Tree 

The version tree focuses on the historic details of a single item. It allows developers to trace why changes were introduced, and integrators to solve merge and promotion issues more efficiently.

Differences and merge

Plastic SCM provides several differences and merge tools to accommodate different kinds of digital assets. While source code managing tools are most widely used, other formats like images and Microsoft Word are also supported.

  •  Code differences. Classical code file differences have been enhanced applying syntax highlight. This makes the code easier to read and follow. Soft gradients and carefully chosen color schemes to display differences also contribute to an overall more comfortable experience.
  •  Image differences. Supporting two modes, side by side or blended, where both images are blended together making it very easy to spot differences. A slide bar controls the level of transparency applied to the images.
  •  Code merge. The 3-way merge is always a complicated process. We applied the same visualization technology previously used for differences, this time a step beyond. Our merge algorithms are highly optimized to resolve automatically as many conflicts as possible, and even for those not automatic, try to suggest the best possible solution before hand.

IDE and task tracking integrations

Plastic for Eclipse

Plastic SCM integration with Eclipse allows developers to carry out any kind of source control operation from their development environment. This is an easy way to improve productivity as every part of your development can be achieved from the same tool. From Eclipse, developers are able to keep the whole project clearly under strict control from the source control. You can easily do any kind of operations implemented by Plastic SCM. such as checkouts, checkins, adding new elements, checking differences with previous versions, consulting their development’s history, obtaining versions, etc..Refactor support is also available. Developers can also manage the project’s structure from their development environment thanks to renaming and moving files and folders operations.

Plastic SCM for Eclipse integration is available for the following platforms:

Eclipse version 2.1.2+
Eclipse 3.1
Eclipse 3.2

Plastic SCM for Visual Studio

Plastic SCM integration with Visual Studio allows developers to perform common version control operations from their development environment, making SCM transparent to the developer. This would bring an increase on their productivity as every task would be done within the same tool.

From Visual Studio developers can keep under control the whole project working transparently on their source code. Operations such as check out and check in, adding new elements, the ability to see the differences with previous versions, checking the history of the project, obtaining different versions…they are all easily available.

Furthermore, from Visual Studio 2005 developers are able to manage the projects´ structure from their development environment due to the ability of renaming and moving both files and folders. Traditional SCM products do not support this kind of operations or are very slow and difficult to manage. Plastic SCM, by its full project’s structure versioning and its fully integration with Visual Studio, allows moving files or folders and always keeps the elements history.

Starting to work with Visual Studio and Plastic SCM is very easy. You would only have to create a new project and add it to the source control so it will be ready to start working. Plastic SCM is meant to allow the developer to spend his time only doing his job and not having to learn how to use new tools. It also provides useful functionalities in order to increase the development productivity.

Isolated development on branches allows each developer to make changes on his code without interfering with the rest of the team and they do not interfere with his work, so it provides parallel development, the possibility of always returning to a previously modified version and it increases both stability and productivity.

Plastic SCM integration with Visual Studio is available for:

  • Microsoft Visual Studio 6.0 +
  • Microsoft Visual Studio .NET 2003
  • Microsoft Visual Studio 2005
  • Microsoft Access

Transparent integration

Plastic SCM integrates with most modern user directory technologies out of the box, providing a very fast setup and having little or no maintenance requirements.

Active Directory integration. Provided that clients and servers are inside a Windows Active Directory domain, no questions are asked. Server will get known users from the domain, and clients will transparently validate using Windows integrated authentication against it.

LDAP authentication. Two different modes are available. First one allows Unix based clients, or even Windows ones outside the domain, to be authenticated against a PlasticSCM server getting its data from an Active Directory. Native LDAP, on the other hand, allows full authentication against regular LDAP servers, that can be running, for instance, on Solaris.

Name authentication. In this mode the Plastic SCM server will retrieve the users from the machine where it is running. Provided that the network set up makes the same users available to both the client and the server, the mechanism will work. This method can be used for NIS based networks.

Name + ID authentication. Same as the Name mode, but user id data is also considered. This is the recommended mode for NIS-based networks.