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=21856>. 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=21856 Request standardized way of finding ant.jar Summary: Request standardized way of finding ant.jar Product: Ant Version: 1.5.3 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] It is common for build scripts to compile their own tasks and then taskdef them. Unfortunately there is then no standard way to find ant.jar to put in the classpath (assuming you use ${build.sysclasspath}=ignore), unless you happen to include a copy of this JAR with your project. You can use ${ant.home}/lib/ant.jar which works with command-line Ant from apache.org but might not work with (1) IDEs which bundle Ant, (2) the RPM from jpackage.org which uses a different directory structure, etc. Suggest a new built-in property, ${ant.jar}, specifically for a JAR file containing central Ant classes you would want to import into custom task sources. (org.apache.tools.ant.*, basic datatypes and utilities, MatchingTask, etc.) Motivation: http://www.netbeans.org/issues/show_bug.cgi?id=35123 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
