tag:blogger.com,1999:blog-5638372.post113960603233263314..comments2023-10-10T05:22:56.347-05:00Comments on binkley's BLOG: A tricky ant trickBrian Oxleyhttp://www.blogger.com/profile/06617364377560752378noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5638372.post-1140548117720623902006-02-21T12:55:00.000-06:002006-02-21T12:55:00.000-06:00You make a good point. Yes, "copy" already has th...You make a good point. Yes, "copy" already has this built in. I picked "copy" only for illustrative purposes. My actual build uses "signjar" and had to work around that "signjar" does not check the timestamps for anything.Brian Oxleyhttps://www.blogger.com/profile/06617364377560752378noreply@blogger.comtag:blogger.com,1999:blog-5638372.post-1140475282103902022006-02-20T16:41:00.000-06:002006-02-20T16:41:00.000-06:00Yes, "uptodate" is very handy.But I don't understa...Yes, "uptodate" is very handy.<BR/><BR/>But I don't understand why you need it here. The "copy" task has similar checking built-in, and will avoid overwriting files that are already up-to-date (unless, of course, you set overwrite="true").<BR/><BR/>I tend to use "uptodate" in conjunction with "checkpoint files", to work around the shortcomings of tasks that don't have built-in up-to-date checking. For instance, the "junit" can't tell when a test needs to be re-run. So, if all my unit-tests pass, I'll create a checkpoint file called "unit-tests-done" in the build-area. Subsequent builds will skip unit-tests unless there is code newer than the checkpoint file.Anonymousnoreply@blogger.com