A developer's environment is provided so that developers can build their components, test the interaction of their components with a message server using a home-made testing tool called "remote control", and integrate their components into the next generation of VC for further experiments.
First, the developers put the source codes into a CVS repository and then use a tool called Maven to do the builds. Maven can automatically organize many things and autogenerate supporting documentation that is made available through a website (also automatic). Maven also provides: change logs, JavaDocs, cross-referenced source code, unit test reports, etc.
Next, a project called Cruise Control is configured to automate the build process. What Cruise Control does is to monitor the CVS repository and when a file is changed it runs all the test and the build. If something breaks it sends an email to the developers that have changed code since the last working build.
Lastly, every project needs a bug tracking solution. There is an open source project called Atlassian JIRA that provides a web based product that has many nice features.
In sum the following tools are provided:
CVS - source code control - https://www.cvshome.org/docs/manual/
MAVEN - it is a build framework that automates many things - one thing is the automatic creation of a project website where javadocs are automatically web enabled http://maven.apache.org/
BUGZILLA - project tracking tool: http://www.bugzilla.org/ or http://130.49.222.93/bugzilla/
CRUISE-CONTROL - http://cruisecontrol.sourceforge.net/
An example of messaging has been prepared and available under CVS. For details please consult http://www.cs.pitt.edu/~chang/231/server/doc/. The messaging example has client and server components. Both the client and the server parts of the example are under the CVS. Also in the CVS is the eclipse project. To run the example first you need to download the CVS and set up your local environment. To run the client and the server you need to set up Axis on your local machine and follows the steps described in VCSetup.doc. Then you can run Eclipse and Bugzilla to test the example. If you succeed in running the example, you will see the following output.
Each user will have a separate "branch" in the CVS, so that all users can share the common root and cooperate in software development. Therefore you need to request a user id and password from the instructor. The id runs from s1 to s9, and the password will be assigned by the instructor.
Please check tips for additional info on setup. If you run into problems, please send e-mail to john.menke@eagleinfosystems.com