DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28046>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28046 Ant includes JARs in working directory ------- Additional Comments From [EMAIL PROTECTED] 2004-09-03 13:57 ------- I agree with the original poster. I hit this behavior today as well and it broke our build system. We have targets to build JARs from a compiled source tree - the JAR output is placed in the same directory as our build file. We also have targets to run an app (for developers) from the compiled source tree. After upgrading to ant 1.6, this system breaks -- the run target now pulls classes from the JAR files, much to the confusion of many. I finally found the new, one-line description in the manual stating that 'all elements of env. var. CLASSPATH are passed as -lib arguments to ant' -- thus they are scanned for JAR files. This is very inconsistent with Java's standard behavior regarding CLASSPATH... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
