Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[SUREFIRE-2016] The MOJO parameter testSourceDirectory is used only in the TestNG HTML, and it should be optional. Javadoc and documentation should be fixed. #472

Merged
merged 1 commit into from Feb 17, 2022
Merged

[SUREFIRE-2016] The MOJO parameter testSourceDirectory is used only in the TestNG HTML, and it should be optional. Javadoc and documentation should be fixed. #472

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 2 additions & 1 deletion ...-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java
View file
Open in desktop
Expand Up @@ -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;

/**
Expand Down
8 changes: 4 additions & 4 deletions maven-surefire-plugin/src/site/apt/examples/inclusion-exclusion.apt.vm
View file
Open in desktop
Expand Up @@ -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.
Expand Down