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 Bouncy Castle where so helpful to supply the JAR that you need to create HMAC integrity checks on their web site. When you use the ant makefile 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
 |  |  |
 | <property
name="jce.download.file"
value="jce-jdk13-114.jar" />
<property
name="jce.download"
value="http://www.bouncycastle.org/download/${jce.download.file}" />
<property
name="lib.jce"
value="${libs}/bc-${jce.download.file}" />
|  |
 |  |  |
Here you can see that the file
http://www.bouncycastle.org/download/jce-jdk13-114.jar
is downloaded and stored in the location ./libs/bc-jce-jdk13-114.jar
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.