Also there's about 10 gazillion times on the project site where we say to run "mvn verify"... could you help us make this more clear?
-Stephen On 23 August 2010 14:48, Stephen Connolly <[email protected]>wrote: > See: http://maven.apache.org/plugins/maven-failsafe-plugin/ > > The Maven lifecycle has four phases for running integration tests: >> >> * pre-integration-test for setting up the integration test environment. >> * integration-test for running the integration tests. >> * post-integration-test for tearing down the integration test >> environment. >> * verify for checking the results of the integration tests. >> >> If you use the Surefire Plugin for running tests, then when you have a >> test failure, the build will stop at the integration-test phase and your >> integration test environment will not have been torn down correctly. >> >> The Failsafe Plugin is used during the integration-test and verify phases >> of the build lifecycle to execute the integration tests of an application. >> The Failsafe Plugin will not fail the build during the integration-test >> phase thus enabling the post-integration-test phase to execute. >> >> NOTE: when running integration tests, you should invoke maven with the >> (shorter to type too) >> >> mvn verify >> >> rather than trying to invoke the integration-test phase directly, as >> otherwise the post-integration-test phase will not be executed. >> > > -Stephen > > > On 23 August 2010 14:46, Stephen Connolly <[email protected]> > wrote: > > 1. put failsafe:verify in verify where it's supposed to be > > 2. don't run "mvn integration-test" but run "mvn verify" (shorter to type > too) > > > > -Stephen > > > > On 23 August 2010 14:28, Benson Margulies <[email protected]> wrote: > >> I have been unable to find a way to make a failure in an integration > >> test result in failing the overall build. I have failsafe:verify in > >> post-integration, and no joy. > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > >
