After SUN released the j2sdk1.4.0/jre/lib/endorsed/xalan.jar . If you installed an out-of-the-box JDK1.4 (e.g. on Windows 2000), the "endorsed" directory does not exist: you'll have to create it by hand. Putting this JAR to another location like lib/ext WILL NOT WORK.
For more on that, you can also check the
Make sure you get the Jakarta Ant Tool from
You can download the sources via WWW in the distribution directory under
This project's CVS repository can be checked out through anonymous (pserver) CVS with the following instruction set. The module you wish to check out must be specified as the modulename. When prompted for a password for anonymous, simply enter "anoncvs" without quotes:
A HTTP interface to browse the sources online is available via
At the command prompt type 'ant test'. If you want to use jikes instead of your default java compiler locate the 'build.xml' file and replace the line
with
The first way to ensure that everything is in place is to run the unit tests. This is simply done by typing ant test. This starts the included JUnit test cases. Actually, we do not have complete test coverage, but as a first start, it works.
To see how the distribution works, simply run ant mega-sample to let ant execute several examples from the src_samples/ directory.
| build.xml | Top level |
| LICENSE.txt | License for the software |
| README | Build instructions |
| Readme.html | Web page redirect required for building documentation |
| STATUS | Current source code status information |
| data/ | Directory containing sample data files and test vectors for the unit tests |
| doc/xml/ | Directory containing documentation, in XML form |
| src/ | Directory containing source code for the core library |
| src_samples/ | Directory containing source code for samples |
| src_unitTests/ | Directory containing source code for unit tests |
There is no JCE bundled together with this distribution. Living in Germany, I had no problem to include the JCE in this software package but then I realized that the Apache Project is hosted in the US where some export restrictions apply to the cryptographic primitives.
Well, how do we solve this problem? The nice guys from the build.xml and simply say ant compile or ant get-jce, ant tries to fetch this JAR from the australian server. After that step, the compilation works completely.
The ant make tools initiates an automated download of the BouncyCastle JCE. The file is downloaded into the libs/ directory and a "bc-" is prepended to the filename. This is done because we want the provider name (bc means BouncyCastle) being visible in the JAR's filename.
If you are a little paranoid like all security people and don't want ant to make automated downloads or your firewall doesn't permit it (preventing programs "phoning home"), look in the ./build.xml file for the properties called
Here you can see that the file
is downloaded and stored in the location @@lib.jce@@
If you do this by hand (pointing you favourite web browser and download it yourself), simply put a "bc-" in front of the filename and put it to ./libs/, then ant won't try to make a download.
After SUN released the j2sdk1.4.0/jre/lib/endorsed/xalan.jar . If you installed an out-of-the-box JDK1.4 (e.g. on Windows 2000), the "endorsed" directory does not exist: you'll have to create it by hand. Putting this JAR to another location like lib/ext WILL NOT WORK.
For more on that, you can also check the