Author: pgier
Date: Thu Aug 20 16:39:55 2009
New Revision: 806246
URL: http://svn.apache.org/viewvc?rev=806246&view=rev
Log:
[SUREFIRE-529] Debugging example should use forkMode=never instead of
forkMode=none
Modified:
maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/debugging.apt
Modified:
maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/debugging.apt
URL:
http://svn.apache.org/viewvc/maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/debugging.apt?rev=806246&r1=806245&r2=806246&view=diff
==============================================================================
---
maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/debugging.apt
(original)
+++
maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/debugging.apt
Thu Aug 20 16:39:55 2009
@@ -35,14 +35,14 @@
You can force Maven not to fork tests by configuring the <<<forkMode>>>
configuration parameter.
+---+
-mvn -DforkMode=none test
+mvn -DforkMode=never test
+---+
Then all you need to do is debug Maven itself. Since Maven 2.0.8, Maven has
shipped with a "mvnDebug" shell script that you can
use to launch Maven with convenient debugging options:
+---+
-mvnDebug -DforkMode=none test
+mvnDebug -DforkMode=never test
+---+
Then you can attach Eclipse to Maven itself, which may be easier/more
convenient than debugging the forked executable.
\ No newline at end of file
