Vincent Massol wrote:
Hi,
I've just discovered the Ant xmltasks task: http://www.oopsconsultancy.com/software/xmltask.html
The xmltask stuff is indeed pretty nice. But I'm generally reluctant to add dependancies to the build (as you probably know by now :-) ). Unless something really adds value and cannot be relatively easily be done otherwise, I prefer sticking with "core" stuff like Ant or W3C-DOM...
It's very nice and I'm sure we could use it in our Cactus build. Some ideas:
- use it in the servlet sample build in order to support the different J2EE API and Clover/Non-Clover builds
Yeah, currently we do that by conditionally commenting out sections using Ant filters. While not perfect, it works :-)
- use it in the Eclipse projects to replace the version from "1.5.0" to a version with a date (ATM, I've done a hack for that).
Hmm, I don't know which hack you are referring to here, so I can't really comment.
- use it at runtime in our webxmlmerge tasks. That would allow to remove 90% of the custom code we've had to write I guess.
I'm -1 adding xmltask as a runtime dependancy. If we wanted to simplify the XML access/manipulation code (in the classes ApplicationXml and WebXml), we should consider using the XPath API provided by Xalan (org.apache.xpath.XPathAPI). This API is also included in JDK1.4, it seems.
What do you think?
Thanks -Vincent
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
