[ http://jira.codehaus.org/browse/MNG-2142?page=comments#action_60661 ]
Brett Porter commented on MNG-2142: ----------------------------------- This flies in the face of the current lifecycle design. The only way I see this is being feasible is if we do use the pre/post automated phase wrappers and make their semantics to behave in this way. The alternative is to not fail from the integration-test goal, but set a property, then fail from the post- phase after everything is done. Sounds hacky though. > Forcing execution of the post-integration-test phase > ---------------------------------------------------- > > Key: MNG-2142 > URL: http://jira.codehaus.org/browse/MNG-2142 > Project: Maven 2 > Type: Improvement > Components: integration tests > Versions: 2.0.3 > Reporter: Vincent Massol > > > The post-integration-test phase needs to always be called even in case of > tests failures in the integration-test phase. > For example when using Cargo the container may be left running if the > post-integration-test phase is not called... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
