Table of Contents
The Jamama source code repository has moved to Sourceforge. Watch mode is on, so you need to use the command cvs edit to publicize your intention to change source code.
See the Resources and Traditional Client sections of my CVS HOWTO.
Before you run these commands, do yourself a favor and make a .cvsrc file containing
cvs -z6 -q
This will use compression to speed up CVS transfers, and will turn off the Windows-like verbose messages that CVS is fond of. Users of third party CVS clients or wrappers will have to find out how to set these default for their client.
Unless you enjoy typing your password over and over, create a ssh key and upload it to the Sourceforge CVS server under your Account Options page at Sourceforge.
Typical CVS development procedure
Edit files, unedit files, update, run ant commands to your heart's content. Here is a very small subset of some stuff you could do.
Example 4.3. Preparing for committing.
$ cd /path/to/jamama-dev $ cvs update -d # You will be notified of conflicts
Edit conflicting files (they are labelled with C in the update listing), and make sure the code still builds. Repeat until the cvs update command shows no C's. Continue once all conflicts are resolved...
$ cvs commit -m 'Your comment'
You can, of course, commit resources individually or by subdirectory branches. You will want to check in files individually if your changes warrent different log messages for different resources-- Use meaningful log messages!.