[snip] > If it works locally, then why don't you keep it locally, as I do ? > You wrote that: > " > Ok, I've re-run the latka build on my machine with the latest xerces and > xalan, and still can't reproduce this. > "
> Or is it that you're using an older Xerces version? > I agree that Xerces could be having a bug, but if putting it locally > resolves the problem, why not fix it now anyway? I've never tested with the DTD locally. I've tested it remotely and it works for me. > > Have you lost it? Maven is not involved in this problem. I don't > > understand what your fixation is with Maven. I'm trying to fix a > > Gump/Latka problem here. > Because Latka AFAIK uses Maven for the documentation (the site is > Maven-built), and the problem comes from the xdocs. Ok, you'd think I'd know what the Latka build process is, and how it's triggered, since I'm almost the only active developer on it. And I've already stated that the build process Gump is using doesn't use Maven. You are showing your ignorance here. Go read the build.xml in Latka's source tree and look for Maven. > Or it doesn't use Maven, and I'm puzzled :-? Not puzzled. Wrong. > Also, don't Maven projects make the Gump descriptor automatically from the > POM? Yes. > Is your descriptor hand made? Yes. > Sorry for the noise, I just thought that since you seem to be using Maven, > they might be interested too in solving this issue. Nope. Again this has absolutely NOTHING to do with Maven. Go read the build.xml from Latka that Gump is using. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
