Mark,
This has been my approach as well. Have a .build file at a given
directory level be responsible for building itself and nested
subdirectories. I would often have a common .build file that contains
common propeties that all the other .builds would include.
Ian
Attached is an example of using nested build files.
This example closely follows how we organise our build files here. I am not
certain that it is the best way, and would be open to suggestions on better
techniques.
Creating this example has made me consider the whole topic of 'NAnt Best
Practices'.. but that can wait for another day.
-MG
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
