summaryrefslogtreecommitdiff
path: root/textproc/jdom
AgeCommit message (Collapse)AuthorFilesLines
2008-07-14Mark as destdir ready.joerg1-1/+3
2008-05-25Explicitly add pax dependency in those Makefiles that use it (or havejoerg1-1/+2
patches to add it). Drop pax from the default USE_TOOLS list. Make bsdtar the default for those places that wanted gtar to extract long links etc, as bsdtar can be built of the tree.
2008-03-04Resign from maintaining a lot of packages, so everyone is free to updaterillig1-2/+2
them at will.
2008-02-28Replaced the deprecated INSTALLATION_DIRS_FROM_PLIST with AUTO_MKDIRS,rillig1-2/+2
to shut up the pkglint warnings.
2007-10-19Imported jdom.rillig4-0/+209
There is no compelling reason for a Java API to manipulate XML to be complex, tricky, unintuitive, or a pain in the neck. JDOM[TM] is both Java-centric and Java-optimized. It behaves like Java, it uses Java collections, it is completely natural API for current Java developers, and it provides a low-cost entry point for using XML. While JDOM interoperates well with existing standards such as the Simple API for XML (SAX) and the Document Object Model (DOM), it is not an abstraction layer or enhancement to those APIs. Rather, it provides a robust, light-weight means of reading and writing XML data without the complex and memory-consumptive options that current API offerings provide.