1 The following is a description of the JARs included with JDOM.
2 More information about the JARs can be found by reading the files
3 accompanying the JARs. Note that the build scripts (build*) take
4 care of adding the proper JARs to the path for building. However
5 you need to set your classpath properly for runtime execution.
10 JDK 1.4 includes XML parser and transformation classes, so if you're
11 using JDK 1.4+ you don't really need to worry about most of the JARs
12 in this directory. However, you might want to add xerces.jar and
13 xml-apis.jar to your classpath so JDOM will use Xerces 2.4.0 instead
14 of the default JDK parser Crimson 1.1. You can also use xalan.jar to
15 use Xalan 2.5_D1 instead of the older Xalan that comes with the JDK.
18 For JDK 1.3 and earlier users, you'll want to add xerces.jar,
19 xml-apis.jar, and xalan.jar to your classpath. Or you can use any
20 third party parser too.
22 All users should add jaxen-core.jar, jaxen-jdom.jar, and saxpath.jar
23 to their classpath to use the XPath features in JDOM.
29 Used for building JDOM. The build scripts include it automatically.
30 Don't include it in your runtime path.
34 The popular Xerces XML parser. Place these two JARs at the head of
35 your classpath and Xerces will be used as your parser.
38 An XSLT processor. Included in J2SE 1.4+. Put this in your
39 classpath if you're doing transforms on older J2SE versions. To use
40 the newer Xalan with J2SE 1.4+ see
41 http://xml.apache.org/xalan-j/faq.html#faq-N100CB.
46 These JARs support the XPath feature of JDOM. Put these in your
47 classpath if you're using XPath.
52 This JAR is created during the build process and put in the "build"
53 directory. This contains the org.jdom.* classes, and you should add this
54 JAR to your classpath when using JDOM.