Instructions for building Bodington
(Windows Specific but could be easily adapted for other OS)

0) Use Netbeans 3.5/JDK 1.4.2 bundle and download RMI support for
Netbeans. Use WinCVS 1.2 to obtain the source code.  You need to
install some optional packages in the runtime part of the JDK by
copying jar files into 
C:\Program Files\j2sdk_nb\j2sdk1.4.2\jre\lib\ext
The required packages are;
Java Mail, Java Activation.  If you intend to run Bodington
from the same JDK then also install your JDBC driver this way
but that isn't required for compiling and building Bodington.

1) Use anonymous access to sourceforge to fetch the source code
to the directory called c:\BodBuild\bodington_2_1
Some example commands are;

cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/bodington login 
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/bodington -r HEAD -d C:\BodBuild\bodington_2_1 export bodington_2_1 
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/bodington logout

You might want to use a checkout command instead of export and 
you might want to specify a tagged version of the source code
rather than the latest version.


2) Create a Netbeans project and mount the following file systems;
c:\BodBuild\bodington_2_1\
c:\BodBuild\bodington_2_1\src\
C:\Program Files\j2sdk_nb\j2sdk1.4.2\lib\tools.jar


3) Compile all the source files in c:\BodBuild\bodington_2_1\src\.
NetBeans should recognize which classes need RMI stubs and generate 
them for you. (Only if you have installed optional RMI support 
using the Update Centre command on the Tools menu).


4) Compile the bodserver.jarContent file to produce an updated
bodserver.jar file.  If you add new packages to the Bodington source
files you will have to update the bodserver.jarContent file to include
those new packages.


5) If you change code that will be included in applets for the 
users of your Bodington installation, compile the bodapplets.jarContent
file.  This will produce the file management applet jar file to put in 
the bodington web app.  You will need to produce your own signing certificate 
and sign the jar file. If you haven't modified the source for the applet 
and haven't added more applets you should avoid rebuilding the jar file 
and use the one that has already been signed by the University of Leeds.

6) Run compiletemplates.bat to convert HTML templates into Java classes.

7) Run pack.bat to package up a Tomcat installation with Bodington
pre-installed in it.  This batch file does the following work;

 a) Packages an almost standard copy of tomcat 4.0.3-LE-jdk14 into
 a zip file.  (The only thing that is non-standard is that non-essential
 web applications have been deleted.)

 b) Adds files from the directory tomcatadd.  This replaces some
 configuration files, adds some java archives and adds the bodington web
 application to the tomcat installation files.

 c) The packaged tomcat/bodington installation is packed into a java
 archive Install.jar with a single class java installation application.
 This can be run with the command;
 java -jar Install.jar

 d) The bodington web app is also packaged up in the file bodington.war so
 that it can be installed into other servlet API compliant web servers.

You could optionally sign the Install.jar file if you intend to distribute it
to others.