On Tue, 9 Nov 2004, Eric Pugh <[EMAIL PROTECTED]> wrote: > The second to last build issue for Fulcrum concerns Fulcrum DVSL > Impl. Everything builds nicely, but the unit test is failing:
I'm not completely certain that Maven's test plugin (is that the correct term?) honors jar overrides, so I'm not completely sure which classpath your tests see. Could you echo out java.class.path inside of your tests to see what is going on. > I have inlined the text of the error. The issue is something > missing on Jaxen. However, I have in my Gump descriptor (but not in > Maven) a dependency on Jaxen. So how do you compile your code with Maven if you don't specify the dependency at all? Is the version of Jaxen used Maven "helping out"? This scares me more than a bit. > I notice in the jaxen.xml project file there are two different ones. > A packaged with dom4j and a standalone. Do I maybe want the > packaged with dom4j? This is in order to break a cyclic dependency between jaxen and dom4j. The resulting jars should work the same way, but only "jaxen" has been compiled against the same dom4j version you use, so you probably want to use that. > I went and checked, and org.jaxen.JaxenException is still part of > CVS HEAD for jaxen... IIRC it has changed its parent class, though. Saxpath moved around a bit. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
