The *only* way to make surefire use threads is to set the <parallel> attribute to some legal value. Use mvn help:effective-pom to see if this is set. I can see from your log output that this is not set, so this is something happening in your code/libs.
I might suggest using -Dmaven.surefire.debug=true and attach a debugger to the tests in question to inspect the call stack/threads to find out WTF is going on. Kristian 2012/7/27 Wayne Fay <[email protected]>: >> Maven version 3.0.1 >> maven-surefire-plugin version 2.11 >> I haven't set other than exclude and include optional parameters of >> surefire. >> JUnit 4.10 >> So, I believe that surefire is using junit 4 provider. >> JRE version 1.6 >> OS: Windows XP > > Can you try Maven 3.0.4 and Surefire 2.12? Also perhaps try specifying > forkMode=never in Surefire. And finally check "mvn help:effective-pom" > to be certain there is not some additional Surefire configuration > coming in from a parent etc that you did not even realize is impacting > your build. > > Hopefully Kristian will see this thread, he is the expert in these areas... :) > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
