Project
  News and Status
  Mission
  Specification
  JavaDoc
  FAQ
  Quotes

Downloads
  Binaries
  Source
  Documentation

Get Involved
  Overview
  Mailing Lists
  Search JDOM Lists

Credits
  Who We Are
  Acknowledgements
 

We provide the JDOMTM source code for anyone who wants it. In general, source code is intended for developers or users who wish to get more involved with the project.

For those of you looking for the JDOM binaries you can find them here.

CVS Access
 With CVS access everyone can view the most current source at any given instant. We recommend people reporting bugs and submitting patches use CVS to ensure they're working with the latest source. We recommend casual users download the latest milestone release. To check out code using CVS, simply use the following commands (if you are using a GUI CVS client, configure it appropriately).

cvs -d :pserver:anonymous@cvs.jdom.org:/home/cvspublic login
password: anonymous

cvs -d :pserver:anonymous@cvs.jdom.org:/home/cvspublic co jdom
cvs -d :pserver:anonymous@cvs.jdom.org:/home/cvspublic co jdom-contrib
cvs -d :pserver:anonymous@cvs.jdom.org:/home/cvspublic co jdom-test

The "jdom" modules is the core of JDOM; the "jdom-contrib" module contains interesting and useful add-ons for JDOM; the "jdom-test" module contains the JDOM test suite. See the README.txt file in the root directory of each module for more information.

The cvs command line program can be found at http://www.cvshome.org. Right now they don't seem to offer binary builds, so for your convenience you can download CVS for Windows from our site. Note that Windows users running CVS must have a HOME environment variable assigned where CVS can store state files. If HOME is not already assigned, it may be assigned using the command "set HOME=c:\".

Release Source Drops
These are the stable, publicly released JDOM builds. Rigorous testing goes into a release build, ensuring you can run it in your production applications without fear of major bugs or trouble.

Milestone Source Drops
Milestone builds indicate large additions in functionality, or pre-release, feature-frozen builds that may soon become release builds. Although generally stable, they often contain new features that are still being tested for their value and usability. These are great for developers and users trying to see what is coming in the next versions of JDOM.

  • We've had no milestones since 1.1.
Daily Source Drops
Daily source drops are just that - whatever state the code is in at the end of a day, this is it. Hopefully nobody is checking things into CVS at the time! There are no guarantees on the functionality of a nightly build, but you are getting the latest and greatest in new features and experimental functionality.