cattails

Blue Marsh Softworks

 Site Index
 o java projects
 o about me
 o search

 My Java
 o java tips
 o java faq
 o contributing
 General Java
 o JavaSoft
 o Developer Connection
 o The Java FAQ
 o Java Glossary

 JSwat
 o download
 o documentation
 o faq
 o mail lists
 o contributing
 o bugs
 Related Software
 o JPDA
 o Emacs JDEE
 o JDBTool
 o jEdit plugin
 o Jenus
 o NetBeans
 Related Links
 o Top Ten Reasons Not to Use a Java Debugger in School

Preliminaries

Before continuing to read this page, please read the general notes on contributing to this or any project hosted on this site.

Revision Control

If you wish to get the very latest JSwat code, you will need a Subversion client. This is explained elsewhere. The JSwat code is available at the URL http://www.bluemarsh.com/repos/jswat/trunk and can be accessed using the following Subversion command:

$ svn co http://www.bluemarsh.com/repos/jswat/trunk -d jswat

To get earlier versions of JSwat (the 1.x series), you will need a CVS client. This is explained elsewhere. Use the commands shown below to fetch all of the required source files.

$ cvs -d :pserver:cvs@bluemarsh.com:/home/cvs login
(password: 'cvs')
$ cvs -d :pserver:cvs@bluemarsh.com:/home/cvs co jswat

Making Changes

Generally if you want to make changes to JSwat, you will already know what you want to do. But if you are just looking to help out in any way, please check out the bug database to find open issues. Bugs that are not assigned to anyone can be worked on at any time. Assign the bug to yourself so others will know you are working on it. You will need to create a Bugzilla account before working on bugs.

It is a good idea to send email to the jswat-dev mailing list to check if anyone else is making a similar change.

Verifying Quality

When making significant changes to JSwat it is important to take the time to verify that everything still works as expected. To this end, please utilize the test checklist documents, provided with the JSwat source code (in "docs/test"). These documents provide points to test and how to test them, for every feature in the program

If you find a bug in JSwat then it may be worth your while to take a number of steps before fixing the problem. One, search the bug database to confirm that you have found a new bug. Two, test using an older release of JSwat to determine if this is a new bug. If so, then you need to fix it. If the bug is pre-existing, then simply log the bug in the database and it will be taken care of.

© Copyright 2000-2002 - Blue Marsh Softworks