Maven Multi-Module builds not honoring failsafe-maven-plugin?

Question

I recently discovered that Hudson was not the problem. In actuality it was Maven itself as the multi-module build was causing the build failure, not Hudson. I just hadn't noticed where the issue actually existed.

Leaving the original question here.

I'm using the failsafe-maven-plugin to run some integration tests. The difference between failsafe and surefire is that failsafe allows failures and does not fail the build.

On my nightly builds there are occasions that a service the integration tests use might be down. In normal builds, the failsafe plugin would let the build continue since the integration tests are allowed to fail. However, Hudson does not seem to respect this and stops the build and produces rain.

I tried to turn the failsafe tests off on nightly builds using -DskipITs. This appears to fail since I'm in a multi module build.

Any ideas on how to get Maven to respect that these tests can fail even though they're part of a specific module?

The project structure is as follows:

-parent
\-jar
\-jar (where integration tests run)
\-war
\-ear

Are these integration tests in a specific directory or in a dedicated module (this is not what I understood)? If not, why not? Can you tell us a bit more about the multi-module structure? What goal do you run for nightly builds, the verify goal? — Pascal Thivent
I'm actually running install on a nightly basis at the top level parent pom. — Mike Cornell

lexicore lexicore · Accepted Answer · 2010-03-29T00:15:40

You can use profiles to make builds a bit different for different environments (nightly builds, releases, normal developer builds and so on).

I'd also try updating the Maven version, there were recently few fixes related to multi-module builds.

Maven Multi-Module builds not honoring failsafe-maven-plugin?

3 Answers