Frequently Asked Questions

Why is the configured Repository Profile not used?

When checking out a working copy with a CVS client, it will save the information to access the repository in CVS/Root files of your working copy. This is done so you don't have to enter any such information again when performing CVS commands on your working copy, like update or commit.

In SmartCVS there exist so-called Repository Profiles which store even more information about how to access a repository than is visible in the CVS/Root file. To check out a working copy from the repository, you have to create and use such a Repository Profile. When performing a CVS command in a working copy (a SmartCVS project), SmartCVS looks at the CVS/Root files of the working copy and searches its list of Repository Profiles. If it finds a matching one, it will use that. If it does not find a matching one, for example because you created a SmartCVS project from a working copy you have checked out with another CVS client, it will create a corresponding Repository Profile automatically. Especially for the ext connection method you may need to change the Repository Profile details, e.g. by specifying the used authentication type (password or private key file).

If you want to use a different Repository Profile for your working copy, you have to change the CVS/Root files accordingly or use the Tools|Change Used Repository of the Professional edition.

When connecting to a GNU CVS server, the connection is reset or stalls

This is a known bug in the zlib implementation of the GNU CVS server (see bug 14840). To work around this problem, unselect the option Use compression for faster client-server-transfer in the project settings (Project|Settings) or default project settings (Preferences, Project/Default Project) or patch the GNU CVS server with the patch provided at the mentioned bug report page.

Which connection methods are supported?

SmartCVS supports pserver, sserver, SSH-1 and SSH-2 (ext) without the need for an external SSH client. It does not support the local connection method, because SmartCVS is just a CVS client, but the local connection method would require server functionality to manage the repository directly.

On a large project, I've got an error dialog (OutOfMemoryError)

If you are using the Windows version of SmartCVS, open the file bin\smartcvs.vmoptions from the SmartCVS installation directory in a text editor. Change the line
vmoption=-Xmx48m
to a higher value (depending on your project size), for instance:
vmoption=-Xmx96m

On Mac OS X do a right-click on the SmartCVS.app and open the Contents/Info.plist file in a text editor. Change the value in the line
<string>-Xmx96m</string>
to a higher value (depending on your project size), for instance:
<string>-Xmx192m</string>

On Linux or Unix just add a line like
_VMOPTIONS=-Xmx96m
after the first commented block.

Scanning the directory structure is very slow

You possibly use a project on a network share. Don't do this, because it significantly slows down file system scanning. Instead store your project on the local hard disk.

Mac OS X: SmartCVS crashed when typing characters

You might have a keyboard which uses a 32-bit driver, whereas SmartCVS runs with 64 bit. Please uninstall the 32-bit keyboard driver and try a 64-bit driver instead, e.g. the default one from Apple.

Windows: SmartCVS crashes when changing the Windows Theme

This is a known problem of the Java Runtime Environment (see also bug 6588271) on Windows XP and newer. It does no harm to your working copy. Simply exit SmartCVS (Project|Exit or right click the tray icon and choose Exit) and restart it. Alternatively, you can configure SmartCVS to use the platform-independent look and feel.

Cannot launch SmartCVS on 64-bit Windows

SmartCVS uses a 32-bit launcher and file-watcher DLL. Starting a 64-bit Java Runtime Environment from a 32-bit launcher or loading the 32-bit DLL from a 64-bit JRE will not work.

Just download the application bundle with (32-bit) JRE and it should work without problems.