On Thu, 30 Oct 2003, Martin Cooper <[EMAIL PROTECTED]> wrote: > I looked at some of the ones I'm (vaguely) familiar with, and it > seems that several of the failures have to do with dom4j not being > available
dom4j doesn't build against any released version of jaxen - and jaxen doesn't build without dom4j. Trying to build jaxen against the latest released dom4j fails because of some jdom changes. The situation is the same with the "traditional" Gump, see <http://gump.covalent.net/log/>. I've already changed the build sequence to try to build jaxen from an installed dom4j and then build dom4j from that jaxen, but you can see the results right now. The alternative would be to build all projects that require jaxen and/or dom4j from the installed packages. This is possible (i.e. they are installed as packaged-dom4j and packaged-jaxen) and can be done for each project if the people who are responsible for the project want to do it. > Personally, I'd be happy to see nags show up for Jakarta Commons > Sandbox and Jakarta Taglibs I think we'd all be *very* happy when nagging (and publishing of build artifacts) will become available again. > (once the dom4j issue is resolved). Unlikely. The issue is known since many months and resulted in daily nag mails. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
