Paul,
I think it's a good idea to move jaxens dom4j implementation to the dom4j project. I've suggested this some time ago on the jaxen mailling lists, but I didn't get much response.
Remark that since dom4j version 1.5, jaxen classes are no longer included in the dom4j-* jars.
regards,
Maarten
Paul R Brown <[EMAIL PROTECTED]> wrote:
Paul R Brown <[EMAIL PROTECTED]> wrote:
Hi, All --
DOM4J and Jaxen have long had a circular dependency, and I hope I'm
not alone in thinking that this is a bad thing. The topic of "what
Jaxen version in dom4j" came up recently, and I've been personally
bitten by the dom4j JAR containing a version of Jaxen that was
incompatible with the Jaxen version that my code elsewhere was
expecting but where dom4j's version was taking precedence...
So, I would like to propose that we make dom4j depend honestly on Jaxen:
1) Jaxen is no longer bundled inside dom4j-*.jar
2) The Jaxen dom4j navigator moves inside the dom4j project.
3) dom4j explicitly calls out which version of Jaxen it depends on.
Thoughts?
-- Paul
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews o n hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
dom4j-dev mailing list
dom4j-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dom4j-dev
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
