> Currently, the only way (AFAIK) to do what you want is to > duplicate the > exec task and surround it with guarding if/ifnot statements:
Eeewww... Ok, I might do that. > I think this is because the xml parser isn't a validating parser, but > the exec task doesn't have the required structure to store the /if/arg > structure. I'm not sure I like this in principle... it would > be nice to > at least have a 'strict' switch, which would use a stricter parser. I think in a perfect world then this should work (i.e, the <if> tag could be used in this way), but if not then at least it should tell you that it won't work. > What would be nice is a patch to exec's arg elements to delay > expansion > of properties in the same fashion as property's value attribute. It > shouldn't be a difficult patch... if people are interested in this > change, and I don't get indication that it's a bad idea, I'll have a > look at it and submit a patch later today or tomorrow. That would be very nice. Thing is, would this just apply to <exec>, because I'm not sure if the same issue would appear in other tasks as well. ********************************************************************** Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you must not copy, distribute or take any action in reliance to it. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of Minorplanet Systems Plc shall be understood as neither given nor endorsed by it. ********************************************************************** ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
