I agree with Ian. It doesn't seem that local tasks would be a common pattern, and it may well be confusing. I'd be more likely to do set up tasks per machine and then leave it at that. His later point about xchemas is also well made.
I think this should be buried in Scott's proposed config file. As he suggested, we should discuss what the config file will allow. For example, buildfile relative path specification for loading tasks. Eric. > -----Original Message----- > From: Ian MacLean [mailto:[EMAIL PROTECTED]] > Sent: Friday, May 03, 2002 2:13 PM > To: Scott Hernandez > Cc: [EMAIL PROTECTED] > Subject: Re: [nant-dev] Task Assembly Loading > > > Scott Hernandez wrote: > > > > >I was imagining that we would probably scan both "." and > "./Tasks". It > >would not seem crazy to me to have build specific tasks in the build > >file directory. > > > >Take for example this directory structure: > > > >myproject > > myproject.build > > tasks (custom) > > src > > src.build > > subdir1 > > subdir1.build > > etc > > etc > > > I'm still not convinced that its a good idea to put those > Tasks in the > build directory. If someone really needs to do it they can > add the path > to the config file. I'm not sure that its a common enough > usage pattern > to warrant making it the default. Is it likely that people will > implement tasks for a single project only ? The other issue > is that if > you have a very big tree with lots of build files calling > each other it > could become difficult to determine which tasks are loaded at > any given > time. ie BuildFileA calls buildFileB which loads some tasks > out of its > basedir and then calls BuildFileC which uses those tasks. However a > different path thru the dependency hierarchy could mean that > buildFileB doesn't get called and those tasks never get > loaded causing > BuildFileC to fail. A contrived example I know. What I'm > getting at is > that the set of available tasks should really be determined when nant > loads rather than changing as various other build files are > called. It > just seems to be adding complexity without gaining much that > you can't > do in other ways. > > I apologise if this seems overly negative. I'm just wary of adding > uneeded complexity > > Ian > > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download > mirrors. We supply the hardware. You get the recognition. > Email Us: [EMAIL PROTECTED] > _______________________________________________ > Nant-developers mailing list [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-developers > _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
