svn commit: r425939 - in /maven/plugins/trunk/maven-surefire-plugin/src/site/apt: index.apt usage.apt

[ar...@apache.org]

Author: aramirez
Date: Wed Jul 26 20:26:09 2006
New Revision: 425939

URL: http://svn.apache.org/viewvc?rev=425939&view=rev
Log:
PR: MSUREFIRE-147

changed some statements from the docs

Modified:
    maven/plugins/trunk/maven-surefire-plugin/src/site/apt/index.apt
    maven/plugins/trunk/maven-surefire-plugin/src/site/apt/usage.apt

Modified: maven/plugins/trunk/maven-surefire-plugin/src/site/apt/index.apt
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-surefire-plugin/src/site/apt/index.apt?rev=425939&r1=425938&r2=425939&view=diff
==============================================================================
--- maven/plugins/trunk/maven-surefire-plugin/src/site/apt/index.apt (original)
+++ maven/plugins/trunk/maven-surefire-plugin/src/site/apt/index.apt Wed Jul 26 20:26:09 2006
@@ -37,7 +37,7 @@
 
 * Examples
 
-  The following examples show how to use the surefire plugin in more advanced usecases:
+  The following examples show how to use the surefire plugin in more advanced use-cases:
 
   * {{{examples/skipping-test.html}Skipping Tests}}
 

Modified: maven/plugins/trunk/maven-surefire-plugin/src/site/apt/usage.apt
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-surefire-plugin/src/site/apt/usage.apt?rev=425939&r1=425938&r2=425939&view=diff
==============================================================================
--- maven/plugins/trunk/maven-surefire-plugin/src/site/apt/usage.apt (original)
+++ maven/plugins/trunk/maven-surefire-plugin/src/site/apt/usage.apt Wed Jul 26 20:26:09 2006
@@ -26,22 +26,26 @@
 
    * POJO
 
-  Which providers are available is controlled simply by the inclusion of the appropriate
-  dependencies (ie, junit:junit for JUnit, org.testng:testng 4.7+ for TestNG). Since this is
-  required to compile the test classes anyway, no additional configuration is required.
+  Which providers are available is controlled simply by the inclusion of the
+  appropriate dependencies (ie, junit:junit for JUnit, org.testng:testng 4.7+
+  for TestNG). Since this is required to compile the test classes anyway, no
+  additional configuration is required.
 
-  Note that any normal Surefire integration works identically no matter which providers are
-  in use - so you can still produce a Cobertura report and a Surefire results report on your
-  project web site for your TestNG tests, for example.
+  Note that any normal Surefire integration works identically no matter which
+  providers are in use - so you can still produce a Cobertura report and a
+  Surefire results report on your project web site for your TestNG tests,
+  for example.
 
-  The POJO provider above allows you to write tests that do not depend on JUnit. They behave in
-  the same way, running all <<<test*>>> methods that are public in the class, but the API
-  dependency is not required. To perform assertions, the JDK 1.4 <<<assert>>> keyword can be
-  used, or you can use <<<org.apache.maven.surefire.assertion.Assert>>>.
+  The POJO provider above allows you to write tests that do not depend on
+  JUnit. They behave in the same way, running all <<<test*>>> methods that are
+  public in the class, but the API dependency is not required. To perform
+  assertions, the JDK 1.4 <<<assert>>> keyword can be used, or you can use
+  <<<org.apache.maven.surefire.assertion.Assert>>>.
 
-  All of the providers support the following configuration. However, there are additional
-  options available if you are running TestNG tests (including if you are using TestNG to
-  execute your JUnit tests, which occurs by default if both are present in Surefire).
+  All of the providers support the surefire plugin parameter configurations.
+  However, there are additional options available if you are running TestNG
+  tests (including if you are using TestNG to execute your JUnit tests, which
+  occurs by default if both are present in Surefire).
 
   See {{{examples/testng.html} Using TestNG}} for more information.