Use one of the enforcer rules or make a new one to validate the conditionss.
On Mon, May 18, 2009 at 2:59 PM, Stephen Connolly < [email protected]> wrote: > nope. > > that will stop trying to build the current module but continue with the > next module... I don't want the current module to stop after > integration-test but after verify > > I have a sneaky feeling I'm going to have to write a plugin to do this > > but seriously, my use case has got to have been faced by somebody else > already > > Sent from my [rhymes with myPod] ;-) > > > On 18 May 2009, at 18:31, "Edelson, Justin" <[email protected]> > wrote: > > Can you use -fae to do this? >> >> On May 18, 2009, at 12:17 PM, "Stephen Connolly" < >> [email protected]> wrote: >> >> Hey, before you think this guy is crazy, surefire will do that for you... >>> >>> pre-integration-test: jetty:run daemon=true >>> integration-test: surefire:test testFailureIgnore=true >>> post-integration-test: jetty:stop >>> verify: ______:______ >>> >>> so that I can run my integration tests and tidy-up afterwards and then >>> fail >>> the build after the tidy-up... >>> >>> yes, yes, yes I know about putting the tests in a separate module and all >>> that jazz... but this is in some ways a bit cleaner >>> >>> -Stephen >>> >> >> --------------------------------------------------------------------- >> 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] > >
