You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by ah...@apache.org on 2006/04/07 15:40:29 UTC

svn commit: r392289 - /maven/maven-1/plugins/trunk/test/xdocs/properties.xml

Author: aheritier
Date: Fri Apr  7 06:40:26 2006
New Revision: 392289

URL: http://svn.apache.org/viewcvs?rev=392289&view=rev
Log:
reorder properties alphabetically

Modified:
    maven/maven-1/plugins/trunk/test/xdocs/properties.xml

Modified: maven/maven-1/plugins/trunk/test/xdocs/properties.xml
URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/test/xdocs/properties.xml?rev=392289&r1=392288&r2=392289&view=diff
==============================================================================
--- maven/maven-1/plugins/trunk/test/xdocs/properties.xml (original)
+++ maven/maven-1/plugins/trunk/test/xdocs/properties.xml Fri Apr  7 06:40:26 2006
@@ -16,18 +16,60 @@
  * limitations under the License.
  */
  -->
-
 <document>
-
   <properties>
     <title>Test Properties</title>
-    <author email="smor@apache.org">Stéphane MOR</author>
+    <author email="smor@apache.org">Stéphane MOR</author>  
   </properties>
-
   <body>
     <section name="Test Settings">
       <table>
-        <tr><th>Property</th><th>Optional?</th><th>Description</th></tr>
+        <tr>
+          <th>Property</th>
+          <th>Optional?</th>
+          <th>Description</th>
+        </tr>
+        <tr>
+          <td>maven.junit.dir</td>
+          <td>Yes</td>
+          <td>
+            The directory to invoke the VM in. (ignored if fork is disabled).
+	    The default value is <code>${basedir}</code>.
+          </td>
+        </tr>
+        <tr>
+          <td>maven.junit.envvars</td>
+          <td>Yes</td>
+          <td>
+            If fork is enabled, additional environment variables may be passed to the new VM.
+            You can specify some variable separated by a space.
+            Each variable is describe in sub properties. 
+            Sample :
+            <source><![CDATA[
+maven.junit.envvars=LD_LIBRARY_PATH
+LD_LIBRARY_PATH=/usr/local/lib]]></source>
+          </td>
+        </tr>
+        <tr>
+          <td>maven.junit.jvm</td>
+          <td>Yes</td>
+          <td>
+            If this property is set it is used as the JVM for the junit tests
+            to run in. This is passed to the Ant junit task in the jvm property.
+            If maven.junit.fork is not true, this is ignored.
+          </td>
+        </tr>
+        <tr>
+          <td>maven.junit.jvmargs</td>
+          <td>Yes</td>
+          <td>
+            If fork is enabled, additional parameters may be passed to the new VM.
+            You can specify some args separated by a space.
+            Sample :
+            <source><![CDATA[
+maven.junit.jvmargs=-Xmx160m -verbose]]></source>
+          </td>
+        </tr>
         <tr>
           <td>maven.junit.fork</td>
           <td>Yes</td>
@@ -63,24 +105,6 @@
           </td>
         </tr>
         <tr>
-          <td>maven.junit.dir</td>
-          <td>Yes</td>
-          <td>
-            The directory to invoke the VM in. (ignored if fork is disabled).
-	    The default value is <code>${basedir}</code>.
-          </td>
-        </tr>
-        <tr>
-          <td>maven.junit.usefile</td>
-          <td>Yes</td>
-          <td>
-            If this value is set to false, JUnit test run details will appear on
-            the console as the tests are executed. If not, they are stored in
-            a file in the <code>test-reports</code> directory. The default value
-            is <code>true</code>.
-          </td>
-        </tr>
-        <tr>
           <td>maven.junit.printSummary</td>
           <td>Yes</td>
           <td>
@@ -91,48 +115,48 @@
           </td>
         </tr>
         <tr>
-          <td>maven.junit.jvm</td>
+          <td>maven.junit.timeout</td>
           <td>Yes</td>
           <td>
-            If this property is set it is used as the JVM for the junit tests
-            to run in. This is passed to the Ant junit task in the jvm property.
-            If maven.junit.fork is not true, this is ignored.
+            Cancel the individual tests if they don't finish in the given time
+            (measured in milliseconds). Ignored if fork is disabled.
           </td>
         </tr>
         <tr>
-          <td>maven.junit.timeout</td>
+          <td>maven.junit.usefile</td>
           <td>Yes</td>
           <td>
-            Cancel the individual tests if they don't finish in the given time
-            (measured in milliseconds). Ignored if fork is disabled.
+            If this value is set to false, JUnit test run details will appear on
+            the console as the tests are executed. If not, they are stored in
+            a file in the <code>test-reports</code> directory. The default value
+            is <code>true</code>.
           </td>
         </tr>
         <tr>
-          <td>maven.test.dest</td>
+          <td>maven.test.classpath</td>
           <td>Yes</td>
           <td>
-            Specifies the unit test classes directory.  This is the
-            location where the java classes for the test source
-            code will be generated to.  The default value is 
-            <code>${maven.build.dir}/test-classes</code>.
+            Specifies one or more locations that will be added to
+            the classpath when the tests are run. Multiple values
+            can be used; the rules of the ant &lt;pathelement path=&quot;...&quot;&gt;
+            directive apply.
           </td>
         </tr>
         <tr>
-          <td>maven.test.skip</td>
+          <td>maven.test.compile.src.set</td>
           <td>Yes</td>
           <td>
-            Set this to 'true' to bypass unit tests entirely.  Its use
-            is <b>NOT RECOMMENDED</b>, but quite convenient on occasion.
-            Ignored by <code>test:single</code>.
+            The source directories Maven uses to compile test code.
           </td>
         </tr>
         <tr>
-          <td>maven.test.failure.ignore</td>
+          <td>maven.test.dest</td>
           <td>Yes</td>
           <td>
-            Set this to <code>true</code> to ignore a failure during testing
-            (errors are considered failures as well).
-            Its use is <b>NOT RECOMMENDED</b>, but quite convenient on occasion.
+            Specifies the unit test classes directory.  This is the
+            location where the java classes for the test source
+            code will be generated to.  The default value is 
+            <code>${maven.build.dir}/test-classes</code>.
           </td>
         </tr>
         <tr>
@@ -144,24 +168,21 @@
           </td>
         </tr>
         <tr>
-          <td>maven.test.source</td>
+          <td>maven.test.excludeXmlApis</td>
           <td>Yes</td>
           <td>
-            <p>
-              Provide source compatibility with a specific release
-            </p>
-            <p>
-              Corresponds to the <code>source</code> attribute for the ant 
-              <a href="http://ant.apache.org/manual/CoreTasks/javac.html">javac</a>
-              task.
-            </p>
+            If set to yes, the XML APIs will not be added to the list of libraries used for your test cases
+            when forked. This should be used when you provide your own XML APIs library. By default, it is
+            <code>no</code>.
           </td>
         </tr>
         <tr>
-          <td>maven.test.compile.src.set</td>
+          <td>maven.test.failure.ignore</td>
           <td>Yes</td>
           <td>
-            The source directories Maven uses to compile test code.
+            Set this to <code>true</code> to ignore a failure during testing
+            (errors are considered failures as well).
+            Its use is <b>NOT RECOMMENDED</b>, but quite convenient on occasion.
           </td>
         </tr>
         <tr>
@@ -173,37 +194,26 @@
           </td>
         </tr>
         <tr>
-          <td>maven.test.classpath</td>
-          <td>Yes</td>
-          <td>
-            Specifies one or more locations that will be added to
-            the classpath when the tests are run. Multiple values
-            can be used; the rules of the ant &lt;pathelement path=&quot;...&quot;&gt;
-            directive apply.
-          </td>
-        </tr>
-        <tr>
-          <td>maven.junit.jvmargs</td>
+          <td>maven.test.skip</td>
           <td>Yes</td>
           <td>
-            If fork is enabled, additional parameters may be passed to the new VM.
-            You can specify some args separated by a space.
-            Sample :
-            <source><![CDATA[
-maven.junit.jvmargs=-Xmx160m -verbose]]></source>
+            Set this to 'true' to bypass unit tests entirely.  Its use
+            is <b>NOT RECOMMENDED</b>, but quite convenient on occasion.
+            Ignored by <code>test:single</code>.
           </td>
         </tr>
         <tr>
-          <td>maven.junit.envvars</td>
+          <td>maven.test.source</td>
           <td>Yes</td>
           <td>
-            If fork is enabled, additional environment variables may be passed to the new VM.
-            You can specify some variable separated by a space.
-            Each variable is describe in sub properties. 
-            Sample :
-            <source><![CDATA[
-maven.junit.envvars=LD_LIBRARY_PATH
-LD_LIBRARY_PATH=/usr/local/lib]]></source>
+            <p>
+              Provide source compatibility with a specific release
+            </p>
+            <p>
+              Corresponds to the <code>source</code> attribute for the ant 
+              <a href="http://ant.apache.org/manual/CoreTasks/javac.html">javac</a>
+              task.
+            </p>
           </td>
         </tr>
         <tr>
@@ -222,7 +232,7 @@
 basedir=${basedir}]]></source>
           </td>
         </tr>
-       <tr>
+        <tr>
           <td>maven.test.search.classdir</td>
           <td>Yes</td>
           <td>
@@ -237,17 +247,7 @@
             <source><![CDATA[maven.test.search.classdir=true]]></source>
           </td>
         </tr>
-       <tr>
-          <td>maven.test.excludeXmlApis</td>
-          <td>Yes</td>
-          <td>
-            If set to yes, the XML APIs will not be added to the list of libraries used for your test cases
-            when forked. This should be used when you provide your own XML APIs library. By default, it is
-            <code>no</code>.
-          </td>
-        </tr>
-
-       <tr>
+        <tr>
           <td>testmatchpattern</td>
           <td>Yes (required in test:match)</td>
           <td>
@@ -255,7 +255,7 @@
             tests that should run
           </td>
         </tr>
-       <tr>
+        <tr>
           <td>testnotmatchpattern</td>
           <td>Yes</td>
           <td>
@@ -263,7 +263,6 @@
             tests that shouldn't run
           </td>
         </tr>
-
       </table>
     </section>
   </body>