maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From agud...@apache.org
Subject git commit: [SUREFIRE-1013] fix typo: forkCount instead of forkMode
Date Mon, 08 Jul 2013 15:09:51 GMT
Updated Branches:
  refs/heads/master 54c46be0a -> fc9edf9aa


[SUREFIRE-1013] fix typo: forkCount instead of forkMode


Project: http://git-wip-us.apache.org/repos/asf/maven-surefire/repo
Commit: http://git-wip-us.apache.org/repos/asf/maven-surefire/commit/fc9edf9a
Tree: http://git-wip-us.apache.org/repos/asf/maven-surefire/tree/fc9edf9a
Diff: http://git-wip-us.apache.org/repos/asf/maven-surefire/diff/fc9edf9a

Branch: refs/heads/master
Commit: fc9edf9aa88b742245ad62a65215069f8c063510
Parents: 54c46be
Author: Andreas Gudian <agudian@apache.org>
Authored: Mon Jul 8 17:08:30 2013 +0200
Committer: Andreas Gudian <agudian@apache.org>
Committed: Mon Jul 8 17:08:30 2013 +0200

----------------------------------------------------------------------
 .../site/apt/examples/fork-options-and-parallel-execution.apt.vm   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/fc9edf9a/maven-surefire-plugin/src/site/apt/examples/fork-options-and-parallel-execution.apt.vm
----------------------------------------------------------------------
diff --git a/maven-surefire-plugin/src/site/apt/examples/fork-options-and-parallel-execution.apt.vm
b/maven-surefire-plugin/src/site/apt/examples/fork-options-and-parallel-execution.apt.vm
index 5e47b0d..207364d 100644
--- a/maven-surefire-plugin/src/site/apt/examples/fork-options-and-parallel-execution.apt.vm
+++ b/maven-surefire-plugin/src/site/apt/examples/fork-options-and-parallel-execution.apt.vm
@@ -86,7 +86,7 @@ Fork Options and Parallel Test Execution
   that Surefire creates one new JVM process to execute all tests in one maven
   module.
 
-  <<<forkMode=1>>>/<<<reuseForks=false>>> executes each
test class in its own 
+  <<<forkCount=1>>>/<<<reuseForks=false>>> executes each
test class in its own 
   JVM process, one after another. It creates the highest level of separation for 
   the test execution, but it would probably also give you the longest execution 
   time of all the available options. Consider it as a last resort.


Mime
View raw message