I don't like replacing distribution folders with new versions. I keep tools in separate folders with version names. (Certainly you've never had an updated tool with bugs which required a rollback!!)
It's a simple thing to have a config file with properties specifying locations for those tools, then load that config file and reference everything via properties. This makes it easy to keep separate versions of tools around, allows me to nicely organize libraries, plus it's *extremely* simple to get new developers up and running since all they need to do is alter their config file for their envrionment. I can't take credit for this approach. I snarfed it from Hatcher and Loughran's _Java Development with Ant_, where they really lay this out in (painful) detail. Yes, the book is about Ant, but many concepts carry over nicely. Jim > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Thibaut > BarrÃre > Sent: Wednesday, September 29, 2004 3:02 PM > To: Gary Feldman > Cc: [EMAIL PROTECTED] > Subject: Re: [Nant-users] NantContrib [loadtasks] > > > Most of the time for the tools I use (ie CCNet, Nant, NantContrib, > fxcop and so on), I try not to modify the distribution folder, so I > can upgrade more easily (just replace the folder, unzipped). > > That's why I prefer not to modify a config file somewhere. > > my 0.02â > > Thibaut > ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
