my experience with copy is that if the destination file exists already, it doesn't do anything even if you've made changes to the src file(It could be I didn't set some attribute correctly). I used <dependset> to solve this problem. You can define dependent relationship between src and target files. Whenever src files got changed, ant detects it and remove all the target files to force copy to regenerate them.
Jian"Chuck" Ma KMV LLC 1620 Montgomery St. Suite 140 San Francisco, CA 94111 415-352-1157(w) -----Original Message----- From: Steve Loughran [mailto:[EMAIL PROTECTED]] Sent: Friday, December 07, 2001 6:32 PM To: Ant Users List Subject: Re: copying on files changed ----- Original Message ----- From: "Christopher Berry" <[EMAIL PROTECTED]> To: "Ant-User (E-mail)" <[EMAIL PROTECTED]> Sent: Friday, December 07, 2001 3:23 PM Subject: copying on files changed > Greetings, > > We are building many projects independently. Each of these projects build > within their own project structure (i.e. they have their own /src and /build > directories). After compilation, the CLASS files are then copied from /build > into a central deployment area named whatever/classes. This all works well > enough. (Note: we do not compile directly into /classes, or use separate JAR > files, for several reasons) > > So here's my problem. I would like to copy only those CLASS files which are > just compiled from /build into /classes. I think this is possible using the > <uptodate> task with an appropriate <mapper>. But I haven't yet gotten it to > work properly. I'm hoping that one of the Ant gurus on this list might give > me some guidance. By default <copy> only copies files if they are newer than the destination. So it should be all you need. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
