DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14553>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14553 Add support for a separate CLASSPATH ------- Additional Comments From [EMAIL PROTECTED] 2003-03-13 16:25 ------- > Ok - I almost rest my case :) ... > by using taskdef resource/file one can reduce > it to a one-liner, but I still see it as a much > cleaner way to specify the tasks available to ant > from the "outside" instead of locally in each build.xml file Actually, I much prefer this one liner that an ANTCLASSPATH. At least some Ant committers prefer explicit things, and the taskdef at the top of all of your build files makes it explicit they are using custom tasks/types. You'll have a hard time introducing a magic feature when there's a clean and simple explicit way to do the same... --DD
