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.

> -----Original Message-----
> From: Roberto Castro [mailto:[EMAIL PROTECTED]
> Sent: 09 August 2004 16:05
> To: Maven Users List
> Subject: RES: Multiproject:clean problem
> 
> 
> It doesn't make sense Carlos, Running "install", then "clean" 
> to run "install" again. I think "clean" could be used to 
> delete the directories, only this. Why it looks for the dependencies?
> By the way, I'll delete target directory using ant.
>       Thank you a lot.
>       Regards,
> 
> 
>      Roberto de Castro 
>      Analista de Suporte 
>      Cetip - Desus Rio de Janeiro 
>      +55 21 2276-7439 
>      mailto:[EMAIL PROTECTED] 
> 
> 
> 
> 
> -----Mensagem original-----
> De: Carlos Sanchez [mailto:[EMAIL PROTECTED]
> Enviada em: segunda-feira, 9 de agosto de 2004 11:33
> Para: 'Maven Users List'
> Assunto: RE: Multiproject:clean problem
> 
> 
> You only need to make multiproject:install once, so you have 
> dependent jars
> in repo. Then you can run clean as many times as you want 
> without running
> multiproject:install (until you change your dependencies).
> 
> Regards
> 
> Carlos Sanchez
> A Coru�a, Spain
> 
> Oness Project
> http://oness.sourceforge.net
> 
> 
> > -----Original Message-----
> > From: Roberto Castro [mailto:[EMAIL PROTECTED] 
> > Sent: Monday, August 09, 2004 4:29 PM
> > To: Maven Users List
> > Subject: RE: Multiproject:clean problem
> > 
> > My intentions running Multiproject:clean was, exactly, to 
> > clean target directory, before building another project. So, 
> > how can I run Multiproject:install first? It doesn't make 
> > sense. In fact, I run Multiproject:install after "clean".
> > Well, what I'm going to do is, delete target directory using 
> > ant script, because I'm afraid an old file in target 
> > directory could interfer when generating project again.
> > By the way, thank you all for the comments.
> >     Regards,
> > 
> >      Roberto de Castro 
> >      Analista de Suporte 
> >      Cetip - Desus Rio de Janeiro 
> >      +55 21 2276-7439 
> >      mailto:[EMAIL PROTECTED] 
> > 
> > 
> > 
> > 
> > -----Mensagem original-----
> > De: Milos Kleint [mailto:[EMAIL PROTECTED] Enviada em: 
> > segunda-feira, 9 de agosto de 2004 10:41
> > Para: Maven Users List
> > Assunto: Re: Multiproject:clean problem
> > 
> > 
> > Dion Gillard wrote:
> > 
> > >AFAIK, the reactor (which multiproject uses), verifies 
> > projects before 
> > >calling goals on them.
> > >
> > >This means, yes, you'll need all the dependent jars in the 
> > repo before 
> > >doing a multiproject:clean
> > >  
> > >
> > 
> > IMHO it shouldn't do it, at least for the the artifacts of 
> > the projects included in the multiproject clean.
> > 
> > Milos
> > 
> > 
> > >On Mon, 09 Aug 2004 15:33:41 +0200, Milos Kleint 
> > <[EMAIL PROTECTED]> wrote:
> > >  
> > >
> > >>and what about the scenario when I do a multiproject clean the a 
> > >>multiproject build which however failt mid-way.. a subsequent 
> > >>multiproject clean failt, because it cannot resolve all 
> > dependencies..
> > >>is there a way out? it seems liuke one can only do a clean 
> > build after 
> > >>successfully building the multiproject..
> > >>
> > >>Milos
> > >>
> > >>
> > >>
> > >>
> > >>Dion Gillard wrote:
> > >>
> > >>    
> > >>
> > >>>You typically need to do a multiproject:install or 
> > >>>multiproject:install-snapshot before using any other goals.
> > >>>
> > >>>This places the dependent jars in the local repo.
> > >>>
> > >>>On Mon, 9 Aug 2004 10:24:04 -0300, Roberto Castro 
> > <[EMAIL PROTECTED]> wrote:
> > >>>
> > >>>
> > >>>      
> > >>>
> > >>>>Hi, when I run "Multiproject:clean" in my master project, 
> > it tries to find a jar file that was not created yet.
> > >>>>I use an argument passed to Maven (mm_domain) to create 
> > the name of jar file.
> > >>>>Is there a bug in Multiproject:clean? I've looked up in 
> > faq but I didn't find anything about this error.
> > >>>>Here is log:
> > >>>>+----------------------------------------
> > >>>>| Executing clean:clean MM - SPBDns
> > >>>>| Memory: 3M/6M
> > >>>>+----------------------------------------
> > >>>>Verifying dependencies for MM:spbdns Getting failed 
> dependencies: 
> > >>>>[EMAIL PROTECTED]
> > >>>>Attempting to download spbmessage-cetip-snapshot.jar.
> > >>>>Getting URL: 
> > >>>>http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-sna
> > pshot.jar
> > >>>>Received status code: 404
> > >>>>File not found on one of the repos
> > >>>>java.io.FileNotFoundException: 
> > http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar
> > >>>>       at 
> > org.apache.maven.util.HttpUtils.retrieveArtifact(HttpUtils.java:547)
> > >>>>       at 
> > org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:381)
> > >>>>       at 
> > org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:287)
> > >>>>       at 
> > org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:181)
> > >>>>       at 
> > org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact
> > (DependencyVerifier.java:326)
> > >>>>       at 
> > org.apache.maven.verifier.DependencyVerifier.getDependencies(D
> > ependencyVerifier.java:255)
> > >>>>       at 
> > org.apache.maven.verifier.DependencyVerifier.satisfyDependenci
> > es(DependencyVerifier.java:171)
> > >>>>       at 
> > org.apache.maven.verifier.DependencyVerifier.verify(Dependency
> > Verifier.java:97)
> > >>>>       at 
> > 
> org.apache.maven.project.Project.verifyDependencies(Project.java:1365)
> > >>>>       at 
> > org.apache.maven.plugin.PluginManager.attainGoals(PluginManage
> > r.java:510)
> > >>>>       at 
> > org.apache.maven.MavenSession.attainGoals(MavenSession.java:266)
> > >>>>       at 
> > org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.
> > java:342)
> > >>>>       at 
> > org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
> > >>>>       at 
> > org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> > >>>>       at 
> > org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(Mave
> > nGoalTag.java:79)
> > >>>>       at 
> > org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction
> .performAction(MavenGoalTag.java:110)
> > >>>>       at com.werken.werkz.Goal.fire(Goal.java:639)
> > >>>>       at com.werken.werkz.Goal.attain(Goal.java:575)
> > >>>>       at 
> > com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
> > >>>>       at 
> > org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(Mav
> > enAttainGoalTag.java:127)
> > >>>>       at 
> > org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
> > >>>>       at 
> > org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> > >>>>       at 
> > org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(Mave
> > nGoalTag.java:79)
> > >>>>       at 
> > org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction
> .performAction(MavenGoalTag.java:110)
> > >>>>       at com.werken.werkz.Goal.fire(Goal.java:639)
> > >>>>       at com.werken.werkz.Goal.attain(Goal.java:575)
> > >>>>       at 
> > com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
> > >>>>       at 
> > org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(Mav
> > enAttainGoalTag.java:127)
> > >>>>       at 
> > org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
> > >>>>       at 
> > org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> > >>>>       at 
> > org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(Mave
> > nGoalTag.java:79)
> > >>>>       at 
> > org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction
> .performAction(MavenGoalTag.java:110)
> > >>>>       at com.werken.werkz.Goal.fire(Goal.java:639)
> > >>>>       at com.werken.werkz.Goal.attain(Goal.java:575)
> > >>>>       at 
> > com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
> > >>>>       at 
> > org.apache.maven.plugin.PluginManager.attainGoals(PluginManage
> > r.java:634)
> > >>>>       at 
> > org.apache.maven.MavenSession.attainGoals(MavenSession.java:266)
> > >>>>       at org.apache.maven.cli.App.doMain(App.java:486)
> > >>>>       at org.apache.maven.cli.App.main(App.java:1215)
> > >>>>       at 
> > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > >>>>       at 
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
> > orImpl.java:39)
> > >>>>       at 
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
> > odAccessorImpl.java:25)
> > >>>>       at java.lang.reflect.Method.invoke(Method.java:324)
> > >>>>       at com.werken.forehead.Forehead.run(Forehead.java:551)
> > >>>>       at com.werken.forehead.Forehead.main(Forehead.java:581)
> > >>>>WARNING: Failed to download spbmessage-cetip-snapshot.jar.
> > >>>>Root cause
> > >>>>Final Memory: 3M/6M
> > >>>>Total time: 32 seconds
> > >>>>Finished at: Mon Aug 09 12:57:57 GMT 2004
> > >>>>
> > >>>>       Thanks in advance,
> > >>>>
> > >>>>    Roberto de Castro
> > >>>>    Analista de Suporte
> > >>>>    Cetip - Desus Rio de Janeiro
> > >>>>    +55 21 2276-7439
> > >>>>    mailto:[EMAIL PROTECTED]
> > >>>>
> > >>>>----------------------------------------------------------
> > ----------
> > >>>>- To unsubscribe, e-mail: [EMAIL PROTECTED]
> > >>>>For additional commands, e-mail: [EMAIL PROTECTED]
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>        
> > >>>>
> > >>>
> > >>>
> > >>>      
> > >>>
> > >>------------------------------------------------------------
> > ---------
> > >>To unsubscribe, e-mail: [EMAIL PROTECTED]
> > >>For additional commands, e-mail: [EMAIL PROTECTED]
> > >>
> > >>
> > >>    
> > >>
> > >
> > >
> > >  
> > >
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> > 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to