jdom also has a dependency on jaxen, although it depends on which
features of jdom you use (specifically jdom uses jaxen for xpath stuff,
although its a weird inter-dependency thing from what i recall).
Anyway, Hibernate requires jdom; however, Hibernate itself does not use
any of the jaxen-related capabilities of jdom and thus does not require
jaxen be present on the classpath for its own use...
Thomas Diesler wrote:
I see that jaxen.jar is not included in AS50. Therefore the current
jbpem-bpel.sar (1.1.0-Beta4) which also does not include jaxen anymore
but depends on it does not run in AS50
What other component uses jaxen? If there is none, then jbpem-bpel.sar
should include jaxen.jar
More generally, I suggest we radically remove all thirdparty jars that
are not referenced from component-info.xml and make it a requirement
that a component declares its dependencies. This should avoid the
problem of carrying over stale thirdparty jars that nobody knows what
they are used for.
In other words, to answer the question: What component uses jar X? I
only need to scan the component-info.xml(s) for X
cheers
-thomas