But this applies only if there is an existing directory corresponding to the target. If no such directory exists, then it might indeed be much faster to rename the directory, and remove the excluded files.
Can I ask why the <rename> task was deprecated? It seems it's a better fit than the error-prone <move todir=''><fileset dir='' defaultexcludes'='false'/></move>? Involving <move> & filesets to rename one directory or file seems overkill to me. Sure *nix only a mv command, but it doesn't have the notion of fileset, and neither does it exclude stuff automatically. I'd like to know the rationals against <rename>. --DD -----Original Message----- From: Stefan Bodewig [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 1:54 AM To: [EMAIL PROTECTED] Subject: Re: moving slowly > If your <move> is slow, it's because <move> detected some files > shouldn't be moved, and thus cannot simply rename the directory > (although I guess it could, and delete the ones that shouldn't be > moved...). No, the files that are not supposed to be moved could already be present in the target directory. Neither overwriting the existing files nor deleting them would be very nice. 8-) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
