Added maven.junit.forkmode property

git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@227528 13f79535-47bb-0310-9956-ffa450edef68

test/xdocs/changes.xml

@@ -25,6 +25,7 @@
   </properties>
   <body>
     <release version="1.7-SNAPSHOT" date="in CVS">
+      <action dev="carlos" type="add">Added maven.junit.forkmode property</action>
       <action dev="carlos" type="update">Allow multiple patterns in testmatchpattern and testnotmatchpattern</action>
       <action dev="carlos" type="add">Added testnotmatchpattern that can be used in test:match</action>
       <action dev="carlos" type="fix" issue="MPTEST-48">Deprecated testmatch property by testmatchpattern to allow more complex patterns in test:match</action>

test/xdocs/properties.xml

@@ -37,6 +37,21 @@
             <code>no</code>.
           </td>
         </tr>
+        <tr>
+          <td>maven.junit.forkmode</td>
+          <td>Yes</td>
+          <td>
+            Controls how many Java Virtual Machines get created if you want
+            to fork some tests. Possible values are "perTest" (the default), 
+            and "once". "once" creates only a single Java VM for
+            all tests while "perTest" creates a new VM for each TestCase class.
+            Note that only tests with the same settings of
+            filtertrace, haltonerror, haltonfailure, errorproperty and failureproperty
+            can share a VM, so even if you set forkmode to "once", Ant may have
+            to create more than a single Java VM. This attribute is ignored for
+            tests that don't get forked into a new Java VM.
+          </td>
+        </tr>
         <tr>
           <td>maven.junit.format</td>
           <td>Yes</td>