CVS Repository Setup Dialog
Optionally specifies the path to the "cvs" command.
Only required if you do not have cvs installed along the default PATH,
or if you want to use your own private version of the cvs command.
Specifies the CVSROOT (see cvs documentation) for all classes which do not
belong to a cvs-module listed in the CVSRoot-per-module list.
I.e. its the fallback CVSRoot used for all other classes, not listed below.
In ST/X, class packages form a hierarchical tree and are mapped in the cvs
repository to source file containes located in subdirectories below a so called
module root. The module itslef is specified by the first component of a package
path.
For example:
The "Array"-class is found in the "stx:libbasic" package.
Therefore, its module is "stx" and its cvs container is found in the "libbasic"
sub-directory, of the CVS-repository which has been associated to the "stx" module.
Placing your own packages into a separate module (typically, you would use your company name
as module-name) and specifying a separate CVSRoot for this module, allows you to
manage your own classes in a separate source code repository.
Of course, this also allows for multiple independent repositories to be defined and
maintained in bigger organizations.
You can attach to the stx-repository (readOnly) by specifying the following
CVSRoot for the "stx" module:
:pserver:stx@www.exept.de:/stx
A CVS-login is required when accessing this repository for the very first time.
Perform this login either via the cvslogin command-line utility, or by pressing the
login-button in the settings dialog. The pasword for the stx repository is "stx".
Performing a slow CVS-checkOut operation for every class which is visited in
the browser does slow down the systems responses - especially the search functions
senders/string-search etc.) may become unusably slow.
To avoid this, the sourcecode-manager keeps track of already checked-out classes
and remembers those in a cacheDirectory. This cache may grow over time, as
it remembers multiple versions of all classes of which source code has ever
been asked for.
The default location for this cache is "/tmp/stx_sourceCache".
Over time, this directory may grow and should be purged from time to time.
(its is not dangerous, to remove those files, as they will be re-checked out
as required).
You can further speedup source-code access, by setting the "use local sources"
flag. If enabled, the source code manager tries to avoid the checkout my first
searching for a copy of the classes sourcefile along the packagePath.
Be aware, that the source code manager trusts the versionNumber found in the
sourcefile, to correspond to the versionNumber of the compiled class.
Manually editing a sourceFile, will certainly lead to invalid sourcecode
being shown in the browser.
If enabled, code which is about to be checked into the repository is
checked for a number of "considered bad" code constructs.
Among them are:
- Leftover sends of the
#halt-message
- Sends of the
#error-message (i.e. without descriptive text-argument)
Copyright © eXept Software AG, all rights reserved
Doc $Revision: 1.2 $ $Date: 2005/10/11 13:03:12 $