/
README.txt
102 lines (70 loc) · 3.33 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
Introduction to the JDOM project
================================
Please see the JDOM web site at http://jdom.org/
and GitHub repository at https://github.com/hunterhacker/jdom/
Quick-Start for JDOM2
=====================
See http://hunterhacker.github.com/jdom/jdom2/ for learning about JDOM2
How to use JDOM
===============
Please see the web site http://jdom.org/downloads/docs.html. It has links to
numerous articles and books covering JDOM.
Installing the build tools
==========================
The JDOM build system is based on Apache Ant. Ant is a little but very
handy tool that uses a build file written in XML (build.xml) as building
instructions. For more information refer to "http://ant.apache.org".
The only thing that you have to make sure of is that the "JAVA_HOME"
environment property is set to match the top level directory containing the
JVM you want to use. For example:
C:\> set JAVA_HOME=C:\jdk1.6
or on Mac:
% setenv JAVA_HOME /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home
(csh)
> JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home; export JAVA_HOME
(ksh, bash)
or on Unix:
% setenv JAVA_HOME /usr/local/java
(csh)
> JAVA_HOME=/usr/java; export JAVA_HOME
(ksh, bash)
That's it!
Building instructions
=====================
Ok, let's build the code. First, make sure your current working directory is
where the build.xml file is located. Then run "ant".
If everything is right and all the required packages are visible, this action
will generate a file called "jdom2.jar" in the "./build" directory. Note, that
if you do further development, compilation time is reduced since Ant is able
to detect which files have changed and recompile them as needed.
If something went wrong, go to the FAQ at http://www.jdom.org/docs/faq.html.
Build targets
=============
The build system is not only responsible for compiling JDOM into a jar file,
but is also responsible for creating the HTML documentation in the form of
javadocs.
These are the meaningful targets for this build file:
- package [default] -> generates ./build/jdom2.jar and other supporting files
- compile -> compiles the source code
- javadoc -> generates the API documentation in ./build/javadocs
- junit -> runs the JUnit tests
- coverage -> generates test coverage metrics
- eclipse -> generates an Eclipse project (source folders, jars, etc)
- clean -> restores the distribution to its original and clean state
To learn the details of what each target does, read the build.xml file. It is
quite understandable.
Bug Reports
===========
Bug reports go to the jdom-interest list at jdom.org. But *BEFORE YOU POST*
make sure you've tested against the LATEST code available from GitHub (or the
daily snapshot). Odds are good your bug has already been fixed. If it hasn't
been fixed in the latest version, then when posting *BE SURE TO SAY* which
code version you tested against. For example, "GitHub from October 3rd". Also
be sure to include enough information to reproduce the bug and full exception
stack traces. You might also want to read the FAQ at http://jdom.org to find
out if your problem is not really a bug and just a common misunderstanding
about how XML or JDOM works.
Searching for Information
=========================
The JDOM mailing lists are archived and easily searched at
http://jdom.markmail.org.