t();
allGoals.add( "clean:clean" );
allGoals.addAll( goals );
For now, you could submit a patch for the verifier and/or use the
invoker directly.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Friday, August 03, 2007 7:59 AM
To: Maven Developers L
"Brian E. Fox" <[EMAIL PROTECTED]> writes:
> You're not crazy. The verifier always inserts clean. It seems like that
> should be configurable for cases like yoursor perhaps testing something
> that breaks in a non-clean build. See the code:
>
> public void executeGoals( List goals, Map e
h for the verifier and/or use the invoker
directly.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Friday, August 03, 2007 7:59 AM
To: Maven Developers List
Subject: Re: Using maven-verifier
Brian is in the process of writing up how to create ITs from the new
sa
Jason van Zyl <[EMAIL PROTECTED]> writes:
> Brian is in the process of writing up how to create ITs from the new
> sample project we have that is turned into an archetype with the new
> archetype code. We'll be there shortly, but these are made for use
> internally but there are ITs for projects t
Brian is in the process of writing up how to create ITs from the new
sample project we have that is turned into an archetype with the new
archetype code. We'll be there shortly, but these are made for use
internally but there are ITs for projects that projects that don't
have POMs.
On 3 A
