Re: [nant-dev] The Vision...

[Gerry S. <ger...@ya...>]

The bootstrap file would be a build file that would
get the real project build from source control.

The real build file would then know how to get the
rest of the project from source control.

The reasoning is that as a project grows just getting
everything to build the project changes but the task
of getting a single file should be fairly stable and
easy.

However your idea of passing it a web address for the
bootstrap file is very very cool.  Imagine you see the
NDoc project and you want to start hacking the code. 
You go to the project web site and find a copy of the
bootstrap build file.  This would have to be updated
on the project web site anytime it changes - BUT it
shouldn't change very often - only when you change
source code control systems I should think.

Now if you run NAnt with that build file it will be
able to get everything it needs to build the project,
run the unit tests, build the documentation, and
package for a distribution.

With a couple of changes it should be possible to
associate a .build file with NAnt so that if you click
on the link from a web site and choose "Open" then it
all just happens.  This might be better suited to a
GUI version of NAnt instead of the current console
based one though.

--- Jason Diamond <ja...@in...> wrote:
> I like your vision.
> 
> I'm sure that I don't know enough about NAnt yet but
> what do you need in the
> mini bootstrap file? Could you just invoke NAnt with
> a URL to the full build
> file (wherever it may) which would download the file
> and process it
> normally?


__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone.
http://phone.yahoo.com