I tried building Jaxen 1.0beta4 (thanks for the fast release), and,
unfortunately, I found that the test.dom target doesn't work unless I
have DOM4J, JDOM, *and* Electric XML installed. Installing DOM4J and
JDOM was only a minor nuisance, but Electric XML is not
Free-As-In-Speech software, and I cannot even download it without
giving away my e-mail address and having them mail me a URL (and then
they place all kinds of bizarre restrictions on its use); I never
do that, so I don't have it.
It's probably a bad idea to have the default build script for an
open-source library like Jaxen depend on something non-free; perhaps
the Electric XML support can be moved into a separate area that is not
built by default. Ideally, 1.0 can be set up with a core Jaxen
library, and then a separately-built source tree for each of the
adapters, which goes into its own JAR by default, i.e.
jaxen.jar
jaxen-dom.jar
jaxen-jdom.jar
jaxen-dom4j.jar
jaxen-exml.jar
(And, of course, jaxen-full.jar, with everything and the kitchen sink.)
By the way, I'm sticking with the releases rather than the CVS because
I need a definite target release for the NewsML Toolkit -- one package
cannot depend on the up-to-the-minute CVS of another without big
trouble.
Thanks, and all the best,
David
--
David Megginson
[EMAIL PROTECTED]
_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jaxen-interest
