Although I don't have your answer, the key I've found to solving these things
related to the plugins is either in the bootstrap.report, velocity.log, or
velocity.log.1
Sounds like a ${basedir} issue though.
You could try
ant -Dbasedir=<where the maven download is extracted> -buildfile <your custom
build file here>
Might help.
-Peter
----- Original Message -----
From: "Richard Emberson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 28, 2002 5:47 PM
Subject: Calling build-bootstrap.xml from ant
> I've built an ant file that downloads and builds maven .... well almost.
> When I call
> an ant task to operate on the build-bootstrap.xml the build fails:
>
> <ant antfile="${maven.dir}/build-bootstrap.xml"
> dir="${maven.dir}" />
>
> It successfully creates the bootstrap directory in the directory where
> the maven
> code is located and compiles the maven classes
> (bootstrap/classes) and copies over the top-level maven build-XXX.xml
> files; but
> when it gets to doing the plugins it creates a new bootstrap directory
> in the
> directory in which I lauched ant and attempts to put the plugins into
> it.
> The last output is
> [create-build-system] Generating to file
> /home/emberson/tmp-maven/jakarta-turbine-maven/bootstrap/bootstrap.report
>
> It puts the bootstrap.report in the correct directory, but it attempts
> to put
> the plugins in the directory
> /home/emberson/bootstrap/maven/plugins.
>
> I am doing this so that others in my group need only execute an ant file
> to get maven, and
> to document how to do it.
>
> Richard
>
>
> --
> 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]>
