The tool our team uses for source code control is CVS. Below are brief directions for setting up your account and using CVS. Please read the CVS documentation. CVS is not intuitively obvious and you need to understand proper use or you can easily destroy your work. Also your CM person should be able to assist if you have difficulties. If you are new to UNIX, you'll need to learn how to manage your files and use a text editor such as pico or vi. Here is a beginning unix tutorial and a quick command reference to get you started.

Initial Setup Of Your Hornet Account And Source Download

1. SSH to Hornet.csc.calpoly.edu
2. Login to your Hornet account.
3. Edit your configuration file
Type:      vi .mycshrc


4. Add the following line to the bottom of the file, right below the other SETENV line. Replace the letter "X" with the digit that corresponds to your team number.
setenv CVSROOT ~team-jdX/cvsroot


5. Save the file and exit vi
6. Create a directory to hold source files
Type:      mkdir 206Project


7. Make the source code directory the current directory
Type:      cd 206Project


8. Check out the source code and download the files to your account,
Type:      cvs co .    (yes, the last character IS a period)

To Update Source Code

1. Login to your Hornet account.
2. Navigate to your 206Project directory
3. Update your files with the latest files from the repository
Type:      cvs update


4. Perform unit development work.
 
• Hornet has a JDK, so you can edit the files on Hornet using a UNIX editor such as pico or vi, and then compile them with the javac command.
• Alternatively, download the files to your personal computer, make changes, test them, and then upload them back to Hornet.
  
  
5. (Important) Before committing your changes, check once more to make sure you have the latest files
Type:      cvs update
If someone else has updated the files, you will have to "merge" your changes with theirs.  If you skip this step you will destroy someone else's work.


6. Commit changes and upload them to the repository
Type:      cvs commit


7. You will be prompted to update the CVS log.  Be sure to enter an accurate and complete description of your changes.  The Change Manager will periodically check the CVS log and issue penalties for missing or inadequate log messages. 
   
8. Your source code changes will now be merged in with the rest of the project's code.

Putting the version into the file