2.2. Download from the CVS repository

The CVS repository at Tigris is accessible using the pserver protocol. The CVS root is /cvs at cvs.tigris.org. You use your Tigris login and Tigris password.

The first thing you will need to do, is select the CVS client. Most of the description below is about the command line CVS tool, which is available for most operating systems.

Whatever tool you use, do not checkout into a directory that contains spaces in a directory name somewhere in the path! E.g. c:\Documents and Settings\...\My Documents\Java Development\ violates this advise 3 times. Reason: You can not build the documentation. (BTW: Building ArgoUML itself works.)

In case you use the command-line CVS client, the above means that you will set the CVSROOT-variable to :pserver:login@cvs.tigris.org:/cvs where login is your Tigris login. This needs to be done before the first checkout. After that the root will be remembered by the checked out copy.

If you use one of the CVS clients with a graphical user interface, (like WinCVS, GruntSpud, ...), or an IDE with a built-in CVS client (like Eclipse, ...) then configuration will be done by filling in fields. These fields mean the following:

If you used the command line CVS client before, then your Tigris password is stored in the file ~/.cvspass. Some graphical UI CVS clients are able to use this password, in others you'll have to enter it again.

The next thing to do is to login. It is done using the command: cvs login. This only needs to be done once and then the account on your machine remembers this.

Then you do the actual checking out. cvs checkout directory.

The CVS repository directories you need to check out to work with ArgoUML are argouml/lib, argouml/tools, argouml/src_new, and argouml/tests.

If you want to build the documentation you check out the directories argouml/lib argouml/tools and argouml/documentation.

If you want to work with the web site you check out the directory argouml/www.

If you give the argument argouml all of ArgoUML is checked out. That is no problem except for the extra use of bandwidth and disk space but if you have plenty of both, get it all, and eventually you will see how everything is used for a purpose in the project.

If you don't want to acquire a Tigris login to do this you can use the "guest" account with the password "guest". Since the checked out copy remembers the login you used to do the check out, if you do this, you will have to remember to delete this copy and start over if you get a developer role in the project and want to do commits directly.