Hi Gary, >What happens if you just make a change to p22? How would you rebuild it without rebuilding the rest? I am sorry, but I don't understand where is the difference to the current approach. The nant will run over all projects and see that p1, p11, p12,p13 are not changed. So it will not rebuild those. Then it will see that p21 changed and will rebuild it, it also will see that p22 and p23 are not changed. I don't see any problem.
Suppose someone introduces a dependency between p21 and p22. What are the implications for your build process? Do you have to manually change the build script? Yes, but with current <nant> task it is the same. Right? So I see no new implications. Currently you need to pay attention that you build p21 before p22. i.e. that in the <nant> task you include p21 before p22. It would be even simpler using "order" attribute. You would only need to change this one. Have you looked at using CruiseControl.Net for this? Yes, I did. Indeed, it could be solved by CC. But it seems to me to be a workaround and overkill (may be I am wrong), to use the second tool in order to organize a build process. BTW Gmake also have switches for multithreading. With best regards and thanks for the great tool :), Boni ------------------------------------------------------------------------- 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