Jazilla

Participation FAQ Glossary Search Download
Jazilla.Org
   About Us
   Who's Who
   Project News

Jazilla.Status
   Administration
   Front End
   Back End
   Mail & News
   To Do Lists

Jazilla.Developer
   Documentation
   Technologies
   CASE Tools
   Software
   Design Info.
   Offsite Links

Jazilla.Public
   Button Contest
   Jazilla Banners
   Jazilla Slogans
   Portal Contest

Jazilla.Feedback


CVS Repository Instructions

The recommended way to retrieve the source code is via CVS (it's easier to keep your copy of the code up to date). CVS is available from . You should get version 1.9 or later.
Excellent resources are available at (PDF version).

To get the Jazilla code you should ensure that CVSROOT is set to

:pserver:cvs@cvs.jazilla.org:/cvsroot

Here is the information on how to set your environment variables on various platforms

   

Microsoft Windows

SET CVSROOT=:pserver:cvs@cvs.jazilla.org:/cvsroot
(NOTE: you also need to set HOME equal to an existing directory into which some CVS information will be put)
   

UNIX (csh)

setenv CVSROOT :pserver:cvs@cvs.jazilla.org:/cvsroot
   

UNIX (bash)

export CVSROOT=:pserver:cvs@cvs.jazilla.org:/cvsroot

Getting the code

After setting the CVSROOT you should type;

cvs login

(you will be asked for a password, just press return)

Once you have successfully logged in change into the directory into which you want the source code to be put and type;

cvs co javamozilla

When you wish to update your files you should go into the directory javamozilla and type;

cvs update -dP

For those who can check code in

For the privileged few who can check code in, there are two ways:

New code

Type the following, enter the comment when asked;

cvs add filename
cvs commit filename

(Note from Chris Floersch: Use cvs add -kb filename for binary files)

Removing files from the repository (from Chris)

Type the following, enter the comment when asked;

cvs remove filename
cvs commit filename

(Note: The file should be deleted from your hard disk before you type the command)

Updating existing code

Type the following, enter the comment for the check in when asked, and all should be OK

cvs commit filename

(Note from Chris Floersch: Use cvs admin-kb filename before cvs commit filename when updating binary files which were not uploaded as binaries)

For those who can't check in code

If you don't have update access to the repository you should contact one of the following people to get your code checked in;

Person

Modules they are most likely to be interested in...

Giao Nguyen

org.mozilla.mozilla.javafe

Chris Floersch

org.mozilla.mozilla.javafe

Joel York

org.mozilla.mozilla.mailnews
org.mozilla.mozilla.lib.libnet

Laurent Thérond

CASE related information

Thierry Bezecourt

org.mozilla.mozilla.nspr
org.mozilla.mozilla.network

Kevin Kelly

org.mozilla.mozilla.nspr

Final Note

If you have any problems please consult the online manual, mail the list, and as a last resort Email Al ;).