Forcing execution of the post-integration-test phase

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.

As I understand it the pre- and post- integration-test phases are for controlling the integration environment, so I think it is vital that the post is called even on failure.

Is there a semantic already that assumes a post- running means success? perhaps pre- and post- whatever should always run for the phase then the lifecycle is defined as a list of phases (exclusing pre- and post-) each of which will invoke a pre- before and a post- after. I believe this would fix another bug I read, though I cannot remember which.

It's possible to configure the Surefire plugin to continue a build even if it encounters a failure. For example, i have:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<skip>true</skip>
</configuration>
<executions>
<execution>
<id>surefire-ut</id>
<phase>test</phase>
<goals>
<goal>test</goal>
</goals>
<configuration>
<skip>false</skip>
<excludes>
<exclude>**/*ITest.java</exclude>
</excludes>
</configuration>
</execution>
<execution>
<id>surefire-it</id>
<phase>integration-test</phase>
<goals>
<goal>test</goal>
</goals>
<configuration>
<skip>false</skip>
<includes>
<include>**/*ITest.java</include>
</includes>
<testFailureIgnore>true</testFailureIgnore>
</configuration>
</execution>
</executions>
</plugin>

My Unit Tests ends with Test.java and my Integration Tests ends with ITest.java. With <testFailureIgnore>, when Maven encounters a error in a Integration Test it continue the execution, stopping the server. Hope it helps

Wow, this is a pretty bad flaw. What else is the purpose of a post-integration-test phase if not to do clean up after the integration-test phase, regardless whether the tests passed or not (like e.g. shutting down a cargo container). Any chance this can get fixed before 3.x?

Can a flag be set so plugins can determine whether the post-process phase is being invoked after success or failure?

We are are hitting this too. Definitely a fix asap would be much appreciated. The workaround
of setting testFailureIgnore to true causes the whole build to appear to succeed which is not generally what one wants when there are test failures. Paul's idea of a flag would be a helpful workaround.

Actually there is a good solution which is to use the failsafe plug-in. This is designed for integration tests and handles this case very well. The test failures are discovered in the verify phase so the post-integration-test phase is always executed. So I would suggest it's not worth fixing this bug.