To resolve this problem I used the following solution:
The reactor has to be called called using:
ignoreFailures="true" (so it keeps going is there is a failure)
and maven is invoked using
maven -o InfoBUS:clean (-o offline: this way maven ignores the central repo)
<goal name="InfoBUS:clean">
<maven:reactor basedir="${basedir}"
includes="**/${pattern}/**/project.xml"
excludes="**/target/**/project.xml"
goals="clean"
banner="InfoBUS:clean"
ignoreFailures="true"/>
</goal>
Bye
-----Messaggio originale-----
Da: Dion Gillard [mailto:[EMAIL PROTECTED]
Inviato: venerd� 28 maggio 2004 15.37
A: Maven Users List
Oggetto: Re: problem with multiproject:clean when new subproject added
On Fri, 28 May 2004 09:11:27 -0400, Jim Crossley <[EMAIL PROTECTED]> wrote:
>
> What? If you have an ear subproject that depends on a new war
> subproject, you won't be able to invoke the clean goal (in the root,
> to clean the old subprojects, for whatever reason) until you've
> installed the new war subproject. That's just wrong: clean should
> ignore missing dependencies.
We'd all agree, but that's the way it currently is.
There is no facility in m1 currently to ignore dependency resolution
when invoking any goal.
--
dIon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This message is for the designated recipient only and may contain privileged or
confidential information. If you have received it in error, please notify the sender
immediately and delete the original. Any other use of the email by you is prohibited.
�����������������������������������������������������������������
su www.tim.it - Shop -, puoi ricaricare subito il tuo telefonino.
�����������������������������������������������������������������
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
