[jdom-interest] XPath and Jaxen

[Jason Hunter]

Put a forked version of Jaxen under the test area?

-jh-

On Sep 11, 2011, at 5:43 PM, Rolf wrote:

> Well, that's embarrassing. a major road-block for writing jUnit test coverage has come up, and I guess I should have anticipated it...
> 
> So, I have essentially done jUnit coverage of all the 'core' JDOM functionality (org.jdom2.* org.jdom2.input.* org.jdom2.output.*), leaving essentially just the transform and xpath code to go.
> 
> SO I started the XPath code, and I can't even create an XPath instance, because the Jaxen library has internal references to org.jdom.* classes, not org.jdom2.*
> 
> This is an interesting chicken/egg process, how does Jaxen build without JDOM, and yet, how does JDOM build without Jaxen...?
> 
> Still, the basic problem is that I need to create a new jdom2-based 'plugin' for Jaxen, but that plugin is a part of Jaxen, not JDOM.
> 
> For the moment I am going to re-implement the plugin on the JDOM side, but the implications are significant, and need discussions.
> 
> What is the right way to do this migration...?
> 
> Rolf
> _______________________________________________
> To control your jdom-interest membership:
> http://www.jdom.org/mailman/options/jdom-interest/youraddr@yourhost.com