Build Proxool from Source
... SourceForge.net Logo
 
 
 
 
Latest
This is the most recently released version. You can always get the latest code from cvs if you are brave enough.
 

How to use build Proxool from the source

Contents:

0. Get the source

1. Get JDK

2. Get Ant

3. Build


0. Get the source

Get the source package or grab the latest code from CVS. See the download page.


1. Get JDK

Get and install JDK1.2 or later. You can get one from various places but a good place to start is Sun. Actually, we recommend getting at least JDK1.3 if it is available on your platform.


2. Get Ant

You don't have to use Ant to build the source. But it's a lot easier if you do. You need to install Ant on your machine first and full instructions for doing that can be found on their web site. The build script has been tested against Ant version 1.5.


3. Build

Move into the directory containing the build.xml file. Ant automatically looks for this file when you run it. The simplest way to build Proxool is to just run Ant with no arguments:

    ant

will build proxool-x.y.z.jar. You'll find it in the build directory.

For more advanced options you need to pass some properties on the command line

    ant -Dproperty=value -Dproperty=value ...
Property Range Default Notes
build-dir Any valid path; absolute or relative to the build.xml file. build Where to build the source to.
test true, false false Whether to include the test classes.
debug true, false true Whether you want debug information to be compiled. Most libraries ship with debugging turned on these days. The jar ends up being a little bigger but that is outweighed by better reporting.

For example:

    ant

will build the jar file.

    ant -Ddebug=false build-jar

will build proxool.jar without debug information (not recommended)


Note: the Ant task repackage-dependencies takes the dependencies in /jarjar and repackages them into build/lib/proxool-*.jar. These are needed in your classpath if you are going to compile the code within your IDE. You can't use the libraries located in /jarjar directly because the package structure is different.