Hi Marcin, -> Build file of a project I am currently working on grew up in a few -> past days and I am thinking about its division into a few smaller -> chunks. Do you have any thoughts on how to do this do get scalable and -> manageable set of build files? Tasks done by this build file include: -> building the code, setting up test environment, firing the test suite, -> deployment and so on. I'd be grateful for any clues and opinions!
Here's a structure for a somewhat (ok, very:) esoteric use for NAnt: http://svn.berlios.de/viewcvs/subnant/trunk/src/ Just in case you're wondering what it's supposed to do: http://svn.berlios.de/viewcvs/subnant/trunk/README.txt?view=markup A core build file (subnant.build) is used to fire any of the /src/targets. Common setup, teardown code and tasks are in subnant.build, and with the recent fixes in 0.85.rc4, the custom functions and tasks are now in /src/include As the project is built for Subversion administration, it doesn't look much (at all?) like NAnt output when run (installs as: nant -emacs -indent:-8 -quiet -nologo:) and it tries to mimic the Subversion command line interface, so you can get extra help on each target by running: subnant help <target> [<target>] This is certainly not a conventional way of using NAnt, (subverting NAnt for Subversion?:) so YMMV, but it may give you some clues. peace si ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
