Characteristic | Local Service Development | VCS Integration |
Installation method | Installed as a plug-in to Designer | Provided by way of the WmVCS Integration Server package |
Tasks required to support new versions of VCS clients | Reinstall the VCS client plug-in; no Designer upgrade needed | Update the WmVCS package every time a new version of the VCS client is released |
Where configured | Designer | Integration Server |
Number of VCS clients permitted to connect to | Permits Designer to connect to multiple VCS clients | Permits Integration Server to connect to only one of the supported VCS clients |
How version control tasks are performed | Locally, within the Eclipse framework (commands are sent directly between Designer and the VCS client) | Through Integration Server |
Menus and commands used | Uses the VCS client’s menus and commands, which may already be familiar to you | Uses its own commands to access the VCS client, which may require extra time to learn |
VCS clients supported |  Concurrent Versions System (CVS)Subversion (SVN)Microsoft Team Foundation ServerEclipse Git Team Provider (EGit) | Microsoft Visual SourceSafeIBM Rational ClearCaseSubversion (SVN)Exposed Java API that you can use to develop a connection to other VCS clients |
Method of communicating with VCS client | Communicates through Eclipse plug-ins that support versions of the clients; plug-ins are either installed by default with Eclipse or available through third-party providers | Communicates directly with the VCS client |
Assets permitted to maintain | Permits check-in and check-out of all contents of a package, including Integration Server assets and other items that Integration Server does not maintain, such as HTML files | Requires manual check-in and check-out of items that Integration Server does not maintain |
