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=7321>. 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=7321 uptodate task should allow "ANY", not just "EVERY". Summary: uptodate task should allow "ANY", not just "EVERY". Product: Ant Version: 1.4 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Enhancement Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I would like to request an enhancement to the Uptodate task (and Condition/uptodate). It currently only sets the property if the target is more recent than EVERY source file. It would be really nice if I could choose between "EVERY" and "ANY"! I can think of more cases where I would need to do something (jar, compile, etc) if ANY file had been changed. I can't think of near as many where I would care that EVERY file had changed. Here is an example where it would be nice to know if any of the java files or the manifest had changed. If any had change, then need to re-jar, else don't need to bother with that step. <property name="build.dir" value="./build" /> <property name="classes.dir" value="${build.dir}/classes" /> <property name="config.dir" value="./config" /> <uptodate property="jar.required" > <srcfiles dir= "${classes.dir}" includes="**/*.java"/> <srcfiles dir= "${config.dir}" includes="Manifest.txt"/> <mapper type="merge" to="${build.dir}/application.jar"/> </uptodate> "ANY" could also involve an efficiency such that as soon as it found one file that was more recent, it could stop and SET the property (ONE/ANY had been found, no need to continue). This enhancement could greatly increase the performance of this task, and make it more flexible. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
