forgot reply-all again .
---BeginMessage---
[EMAIL PROTECTED] wrote:
A good article, thanks for the link. IMO, It depends on the type of
application -- and the type of user. It also depends on how those items are
included.
Agreed. I'd just read the article yesterday so it was fresh in my
Ian,
I assume you are talking about the quiet attribute. I'm wondering how
this overlaps with previous discussions about logging level.
ie if the
logging level is at a certain level write the error otherwise
don't. I'm
not sure there is a need for the quiet attribute on individual
Simon,
I assume you are talking about the quiet attribute. I'm wondering how
this overlaps with previous discussions about logging level.
ie if the
logging level is at a certain level write the error otherwise
don't. I'm
not sure there is a need for the quiet attribute on individual tasks.
Ian,
If I understand you correctly, you want me to remove the quiet attribute and always
output a message in the log when you try to delete a file or directory that doesn't
exist, right ?
I don't really agree with your remarks, but we live in a democracy ..
So if I update the patch, you'll
[EMAIL PROTECTED] wrote:
If I understand you correctly, you want me to remove the quiet attribute and always output a message in the log when you try to delete a file or directory that doesn't exist, right ?
yeah for now. I don't have a problem with the concept but I think we
should think
Was I understanding correctly from an earlier e-mail that:
delete
fileset
includes name=${the.file.I.want.to.delete} /
includes name=${or.the.whole.tree.I.want.to.delete}
/
includes name=${some.file.that.does.not.exist} /
/fileset
Hi IAn,
I've removed the quiet attribute and made sure that a message wil be logged
(in verbose mode) if you try to delete a file or directory that doesn't
exist.
Can you commit this patch (I updated the NUNit test for the Delete task
too) ?
Thanks,
Gert
(See attached file:
Hi,
I agree that we should perhaps decide not to commit this patch at all ...
But if the Delete task should continue to throw exceptions when you try to
delete a non-existing file or directory, then indeed a new mechanism should
be provided that allows you to check if a file or direftory
So the concensus seems to be : defer the patch until file/Directory
Exists functionality is available.
Ian
Hi,
I agree that we should perhaps decide not to commit this patch at all ...
But if the Delete task should continue to throw exceptions when you try to
delete a non-existing file or
