There's a similar chicken-and-egg issue with the custom Ant tasks for
Tomcat integration. What I do is just copy catalina-ant.jar from my most
recent Tomcat build and stick it in $ANT_HOME/lib. I don't try to build
the Ant tasks and immediately use them. (This would be another argument
for releasing this kind of library separately, even if it was struts or
struts-el specific.)
There are no issues with Ant that prevent a custom task from being compiled *and* used in the same build process. My JavaDevWithAnt [1] project does this quite successfully with a custom Lucene <index> task.
And task JAR's are *not* needed in ANT_HOME/lib generally speaking. It can be convenient (or a burden) for them to be there. Just point the classpath used with <taskdef> to where the libraries are (including any dependencies the task needs too!).
It should be a last resort exception to have to put JAR files in ANT_HOME/lib.
I would love to have a gadget like this for *all* of my tag libraries ...
Again... XDoclet! Get with the program folks! :))
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
