[SUREFIRE-2016] The MOJO parameter testSourceDirectory is used only i…

…n the TestNG HTML, and it should be optional. Javadoc and documentation should be fixed.

maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java

@@ -281,10 +281,11 @@ public abstract class AbstractSurefireMojo
 
     /**
      * The test source directory containing test class sources.
+     * Important <b>only</b> for TestNG HTML reports.
      *
      * @since 2.2
      */
-    @Parameter( defaultValue = "${project.build.testSourceDirectory}", required = true )
+    @Parameter( defaultValue = "${project.build.testSourceDirectory}" )
     private File testSourceDirectory;
 
     /**

maven-surefire-plugin/src/site/apt/examples/inclusion-exclusion.apt.vm

@@ -211,10 +211,10 @@ Inclusions and Exclusions of Tests
 
 * Tests from dependencies
 
-  By default, ${thisPlugin} will only scan for test classes to execute in the configured <<<testSourceDirectory>>>. To
-  have the plugin scan dependencies to find test classes to execute, use the <<<dependenciesToScan>>> configuration.
-  Dependencies can be specified using the <<<groupId[:artifactId[:type[:classifier][:version]]]>>> format, and must already
-  be <<<dependency>>> elements in scope.
+  In order to scan dependencies by the ${thisPlugin} plugin and find the test classes to execute in the dependencies,
+  use the MOJO parameter <<<dependenciesToScan>>> and configure it as necessary.
+  Dependencies can be specified using the <<<groupId[:artifactId[:type[:classifier][:version]]]>>> format, and must
+  already be <<<dependency>>> elements in scope.
 
   <Note:> Support for version, type and classifier was introduced in version <<<3.0.0-M4>>>. When using earlier versions,
   ${thisPlugin} will fail with an <<<IllegalArgumentException>>> if more than groupId and artifactId are specified.