The rational behind using separate dir and file attributes is to make what
you are trying to delete explicit. Admitedly, the number of times you are
likely to delete a directory instead of a file are limited, however it can
happen. Also, we were trying to keep things consistent with the <copy> and
<move> tasks, where the possible abiguity of whether something is a file or
directory is unacceptable.
Glenn McAllister
Software Developer. IBM Toronto Lab, (416) 448-3805
"An approximate answer to the right question is better than the
right answer to the wrong question." - John W. Tukey
Please respond to [EMAIL PROTECTED]; Please respond to
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: RE: Nasty gotcha with new <delete>
On Thursday, October 12, 2000 8:49 AM, Glenn McAllister
[SMTP:[EMAIL PROTECTED] wrote:
> I'll update the docs to make that more explicit. Sorry if this caused
you
> any headaches.
>
> Hmm... would it make more sense to limit a delete to either a dir, a
file,
> or filesets? That would make
>
> <delete dir="${some.dir}" file="somefile.txt" />
>
> illegal and prevent people from possibly blowing things away.
>
<snip>
It might be more clear if there was simply one attribute for the delete tag
specifying all objects to be deleted:
<delete filespec="${some.dir} ${some.file}" />
That way there would be no confusion. I don't see any need to specify
directories & files to be deleted separately. Maybe I'm missing something
here?
Regards,
Corey
