----- Original Message ----- From: "Martin Aliger" <[EMAIL PROTECTED]> To: "! nant" <[EMAIL PROTECTED]> Sent: Wednesday, October 27, 2004 5:15 PM Subject: [nant-dev] xmlpeek verbosity
> Hi all, > > do you think that <xmlpeek failonerror="false"> should emit error message > (BuildException) when no nodes are found? How one could check for existance > of some node, when every attempt is considered error? > > I think it is simmilar thing as delete non-existant folder. Should be > silently ignored atleast if failonerror=false is specified (and emmit > something at Level.Debug) Deleting a non-existing folder should, in my opinion, never cause a error message to be output. But I know that's not the current behaviour. Deleting a non-existing folder could be compared to reading the value of a node that was already read. But the <xmlpeek> task is definitely something different as a user expects a given property to be set to a value. If we don't output anything at a all, when no matching node is found then that property will not be set and users will have a hard time troubleshooting. By outputting a warning or error message, users are at least notified that something did yield the expected result. Gert ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
