Olivier asked me about this on IRC, and I got disconnected, so here goes; If you're running a multi-module build with
mvn -Dtest=Fud -Dmaven.surefire.debug=true test Olivier complained about having to start the debugger for every module, even those that do not contain the test "Fud". I'm not too happy about this, but if you add -DforkMode=always, surfire will only fork on the modules that actually contain "Fud" (and not on the ones without Fud), which is just what you want. This should apply to all surefire versions. This is /at best/ an undocumented "feature" of the current forking logic and I have been working quite systematically to remove/simplify/unify the forking logic to extinguish the differences such as this one. But it's still there, for now ;) Kristian
