Skip to Content.
Sympa Menu

xom-interest - [XOM-interest] Xom and Jaxen dependency

xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: "Steve Loughran" <steve.loughran AT gmail.com>
  • To: xom-interest <xom-interest AT lists.ibiblio.org>
  • Subject: [XOM-interest] Xom and Jaxen dependency
  • Date: Wed, 15 Nov 2006 13:47:07 +0000

Elliotte,

are you by any chance the author of the Xom and Jaxen POM metadata
files? The Jaxen one is a bit of a mess:
http://www.ibiblio.org/maven2/jaxen/jaxen/1.1-beta-8/jaxen-1.1-beta-8.pom

1. it should declare all its dependencies (dom4j, jdom, xerces and
xom) optional, unless they really are required.
2. it should go to a later version of Xom than 1.0b3.

Ivy is particularly unhappy, as it finds a loop:

[ivy:resolve] circular dependency found: [ xom | xom | 1.1 ]->[
jaxen | jaxen | 1.1-beta-8 ]->[ xom | xom | 1.0b3 ]
[ivy:resolve] circular dependency found: [ xom | xom | 1.1 ]->[
jaxen | jaxen | 1.1-beta-8 ]->[ xom | xom | 1.0b3 ]
[ivy:resolve] circular dependency found: [ xom | xom | 1.1 ]->[
jaxen | jaxen | 1.1-beta-8 ]->[ xom | xom | 1.0b3 ]
[ivy:resolve] circular dependency found: [ xom | xom | 1.1 ]->[
jaxen | jaxen | 1.1-beta-8 ]->[ xom | xom | 1.0b3 ]
[ivy:resolve]

There's nothing that can be done about the pom for 1.1beta-8; even if
it gets patched both ivy and m2 are coded on the 'assumption of
infallible metadata', so they never check for updated poms. But the
jaxen release could be patched, or the Xom pom could exclude the stuff
under jaxen so that Xom users don't suffer.

FWIW, the whole XML api dependency model doesn't work well with Maven
and Ivy. The Xerces interface and implementations are not in sync, and
neither tool is smart enough to know that xerces/xerces and
xerces/xercesImpl are both implementations of xerces/xmlApis.

-steve




Archive powered by MHonArc 2.6.24.

Top of Page