SCC Tool Dialog Box
This dialog box let you enter the path to one of the support
SCC tool executable.
Thanks to the built-in scripting technology, we have added an
auto-detection feature which is generally able to fill these
paths for you. Nonetheless you can modify the result of the
detection if it does not fit your purpose.
Currently the supported tools are the following:
| Tool |
Default installation path |
Executable Name |
Tested versions |
| Bazaar |
C:\Program Files\Bazaar |
bzr.exe |
1.17 |
| CVS 1.11 |
c:\usr\bin |
cvs[-1.11].exe |
1.11- |
| CVS 1.12 |
c:\usr\bin |
cvs[-1.12].exe |
1.12+ |
| Darcs |
- |
darcs.exe |
2.4+ |
| Git |
C:\Program Files\Git |
git.exe |
1.7 |
| ionForge Evolution |
c:\program files\ionForge\ionForge Evolution |
cscmdln.exe |
|
| Mercurial (hg) |
c:\program files\mercurial |
hg.exe |
|
| Perforce (P4) |
c:\program files\perforce |
p4.exe |
|
| SubVersion (SVN) |
c:\program files\subversion |
svn.exe |
|
| Visual Source Safe |
c:\program files\Microsoft Visual Studio
[year]\VSS\win32 |
ss.exe |
6.0 to 2005 |
-
Under Unix and Mac OS X:
- Same as Windows, except Microsoft Visual Sourcesafe
which does not exist on these platforms. The
executable don't have the .exe extension and are searched
without it in the PATH environment variable.
Nota Bene:
- We studied the well-founded of integrating with
ClearCase, but the philosophy of ClearCase is different from
most other tools in the regard of listing folders and
accessing files. ClearCase uses the notion of view
specifications which works only with a mapping, it makes the
listing directly in ECMerge unnecessary as you must
access your files and folders directly as in a local
filesystem. Nonetheless we build an integration to use
ECMerge as the visual differ/merger in ClearCase, see
Integration with Configuration Management Systems.
See also
|
