Projects distribute the build.xml. You grab that, do an ant build,
like normal, which pulls down maven, installs, starts a maven build,
which pulls down the project's source, and finally builds.
User's only explicitly have to grab the build.xml, but not explictly
sync down CVS or an entire tarball or anything else.
-bob
On Tue, 4 Jun 2002 [EMAIL PROTECTED] wrote:
> +1 on that one.....but chicken and egg....where do they get the build file
> from?
> --
> dIon Gillard, Multitask Consulting
> Work: http://www.multitask.com.au
> Developers: http://adslgateway.multitask.com.au/developers
>
>
>
>
> Jon Scott Stevens <[EMAIL PROTECTED]>
> 06/04/02 01:49 AM
> Please respond to "Turbine Maven Developers List"
>
>
> To: Turbine Maven Developers List <[EMAIL PROTECTED]>
> cc:
> Subject: Maven auto-installer idea
>
>
> Hey all,
>
> What do you think of the idea of adding a target to the project's
> build.xml
> that will auto-install maven? That way, if you don't have maven installed,
> it will download the latest release (or a specific version) and install
> it?
>
> The idea is that the end user who wants to build a mavenized project
> shouldn't have to go to jakarta.apache.org, download ant (install it),
> download maven (install it) and then build the project they want to work
> on...
>
> -jon
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
