Thanks. That clears up the situation re Ant script. For info, I do often use the jspc run purely as a validation check, in builds that don't do an actual "deploy" (e.g. put the .war into auto-deploy directory, or deliver copies of it to other places for archiving). Also to check the JSP before proceeding with other, sometimes lengthy, pre-deployment steps. I can't speak for anyone else, but those are some of my own reasons for sometimes wanting "manual" JSP translation, separate from actual deployment. (Out-of-container testing of JSP code might be another reason in the near future...).
As for the "-d" option, I do use this already. The issue is that it controls the destination of both the resulting Java source code and the class files produced from them. The (very minor) limitation is that there doesn't seem any way to generate the source code into one location and the class files into another. I can't immediately see any real problems from this, it's just another case of a tool unnecessarily imposing its own decision on where everything is put. Fine until you have multiple such tools with conflicting ideas, or other reasons to organize things differently. Just a little pet hate of mine!
Thanks again,
Mike Kaufman
[Message sent by forum member 'mkaufman' (mkaufman)]
http://forums.java.net/jive/thread.jspa?messageID=291067