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=30558>. 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=30558 Classfileset in jar task does not recognize changed files. Summary: Classfileset in jar task does not recognize changed files. Product: Ant Version: 1.6.2 Platform: All OS/Version: All Status: NEW Severity: Critical Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If a jar file is built with the core <jar> task where the fileset is a <classfileset>, the correct jar is built if the target jar does not exist. If one of the dependent java files is modified, and the jar task run again (leaving the prior jar file in place), the modified file is not detected as being newer than the copy in the jar, and the jar is not reconstructed. This happens even if the the new class file is several minutes new. With verbose output, the file is shown being tested, and is reported up to date: archive: [echo] Ant version=Apache Ant version 1.6.2 compiled on July 16 2004 Ant JDK=1.4 [jar] testing/Junk.class omitted as testing/Junk.class is up to date. [jar] testing/dump/Garbage.class omitted as testing/dump/Garbage.class is up to date. In fact, in the above example Garbage.class is "08-10-04 10:14", and the version in the jar file is "08-10-04 09:30". --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
