On Mon, 9 Aug 2004 16:23:01 +0100 , Peter Bright
<[EMAIL PROTECTED]> wrote:
> Does
> <goal name="multiproject:clean">
> <m:reactor basedir="${maven.multiproject.basedir}"
> banner="Gathering project list"
> includes="${maven.multiproject.includes}"
> excludes="${maven.multiproject.excludes}"
> postProcessing="true"
>
> ignoreFailures="${maven.multiproject.ignoreFailures}"
> collectOnly="true"
> />
> <j:forEach var="reactorProject" items="${reactorProjects}">
> <!-- this list of things to delete is lifted from
> clean:clean -->
> <ant:delete
> dir="${reactorProject.context.getVariable('maven.build.dest')}" />
> <ant:delete
> dir="${reactorProject.context.getVariable('maven.build.dir')}" />
> <ant:delete
> file="${reactorProject.context.getVariable('basedir')}/velocity.log"
> quiet="true" failonerror="false" />
> </j:forEach>
> </goal>
>
> fit your needs? It seems to work well enough.
>
> I imagine it's looking at dependencies because it doesn't know that 'clean'
> doesn't need them.
This is a good alternative.
Maven doesn't know that clean is any different to compile or jar, and
still checks the projects dependencies as it processes them.
--
http://www.multitask.com.au/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
