I built jelly from CVS and replaced the one maven uses with the generated jar, and there's only one failing test case.
This was without replacing dom4j. If we can fix that one test case, we can look at the differences between the new jar and Maven's and work out what the benefit is to moving to the new one and dom4j 1.5. How does that sound? I'd also like to push for a beta release of Jelly soon. -- dIon Gillard, Multitask Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
