Other alternatives:
1) add -Dmaven.test.failure.ignore=true to your mvn command line.
2) use a profile
site-generation
true
While you can certainly configure the surefire plugin in your pom as Tung
suggests this has the potentially negative effect of making y
Just run mvn test, instead of building the surefire report. This way, the
build if there are tests failures (but after having executed all of your
tests for the current module).
@Jon : just do the opposite :) run mvn surefire-report:report instead of
anything else, should build a surefire report,
ll my tests are executed even some of them fail.
- Original Message
From: Dennis Klavans <[EMAIL PROTECTED]>
To: users@maven.apache.org; [EMAIL PROTECTED]
Sent: Thursday, August 3, 2006 2:06:45 PM
Subject: RE: SureFire (and surefire-reports) plugins
This is odd. I just posted a requ
This is odd. I just posted a request for the exact opposite to happen. I can't
get the thing to stop on the first failure. First, are you running mvn
surefire-report:report? If so then perhaps we could help each other by
comparing environments. What version of maven are you using? I am on the
You can configure the surefire plugin like this
org.apache.maven.plugins
maven-surefire-plugin
true
HTH
Tung Nguyen
- Original Message
From: Jon SlinnHawkins <[EMAIL PROTECTED]>
To: users@maven.apache.org
Sent: T
