Gert Driesen wrote: > From: "Bonio Lopez" <[EMAIL PROTECTED]> > Sent: Tuesday, July 25, 2006 6:37 PM > ... > > Another solution for your problem would be to skip initializing > tasks/elements if the value of the "unless" attribute evaulates to true (or > the value of the "if" attribute evaluates to false), but we'll need to > discuss this further. > What's the issue with this? This problem comes up often enough. The intuitive sense of the if and unless attributes is that they should always be evaluated first, and if the result is to skip the task, then absolutely nothing else should happen - no other property evaluations, no validity checks on other attribute values, etc. In an ideal world, I'd go as far as saying it shouldn't even fail if there's a missing required attribute or subelement, but those are usually done at the XML level, meaning they're reported before NAnt even looks at the build file contents.
Gary ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
