Heya Merrill, > If you parse <include> tasks, then you would also (I think) have to parse > properties > since the include pathname could be defined by property expansion. However, > properties can be conditionalized by <if> tasks, so they have to be parsed, > and > properties get defaults by command line parameters so they have to be parsed. > By > the time you're finished, you may have processed most of the build file.
Gotcha, all good points. I'll have to look into it some more obviously! Maybe we can start with the simple version - it would still be useful (at least to me!). ;) Then we can make a more thorough and correct version later. Ideally, it won't be that hard to do the full-on parsing. :) Cheers, Matt ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Nant-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nant-users
