Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Mirror of Apache Xerces2 Java

tag: Xerces-J_2_0_0…

Fetching latest commit…


Cannot retrieve the latest commit at this time

Octocat-spinner-32 data
Octocat-spinner-32 design
Octocat-spinner-32 docs
Octocat-spinner-32 proposals
Octocat-spinner-32 samples
Octocat-spinner-32 src
Octocat-spinner-32 tests
Octocat-spinner-32 tools
Octocat-spinner-32 ISSUES
Octocat-spinner-32 KEYS
Octocat-spinner-32 LICENSE
Octocat-spinner-32 README
Octocat-spinner-32 Readme.html
Octocat-spinner-32 STATUS
Octocat-spinner-32 TODO
Octocat-spinner-32 build.bat
Octocat-spinner-32 build.xml
                Xerces Java Build Instructions

Before building Xerces, you need the source package and tools
package available from the Apache XML Project's distribution
web page:

Download both the and 
files for the appropriate Xerces release (where "X.Y.Z" is the version
number) and extract them in the same directory. If you are using Unix, 
download the equivalent .tar.gz files instead of the .zip files.

You also need to have a Java Development Kit (JDK) version 1.2 (or 
higher) installed on your system. Before initiating any part of the 
build, set the JAVA_HOME environment variable to the installation 
directory of your JDK.

The Ant program is used to build everything in Xerces, including
the documentation. This tool, and the others needed (besides the
pre-requisite JDK) are contained within the tools package. To
make building the packages easier, a Windows batch file and a Unix 
shell script are included.

If you only want to compile the source code and make the JAR files,
run the following command on Windows:

    build.bat jars

or from Unix (make sure that is executable): jars

This will compile all of the source code and generate the JAR
files that are available as part of the binary package. After
building, these files will be located in the build/ directory.

If you want to build everything, including the documentation,
run the build batch file (or shell script) specifying the "all"
target instead of "jars".
Something went wrong with that request. Please try again.