[maven-surefire] branch master updated: [SUREFIRE-1670] wrong "Filtering by Test Class Names" in failsafe "Using JUnit 5 Platform" page

[ti...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

tibordigana pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-surefire.git


The following commit(s) were added to refs/heads/master by this push:
     new de1ccc3  [SUREFIRE-1670] wrong "Filtering by Test Class Names" in failsafe "Using JUnit 5 Platform" page
de1ccc3 is described below

commit de1ccc3edbb7414a38f3b31ac701bde6feb9a6f5
Author: Masahiko Sakamoto <sa...@gmail.com>
AuthorDate: Wed Jun 5 01:08:12 2019 +0900

    [SUREFIRE-1670] wrong "Filtering by Test Class Names" in failsafe "Using JUnit 5 Platform" page
    
    switch "Filtering by Test Class Names" list by maven surefire/failsafe plugin site,
    embed `${thisPlugin}` to some section title.
---
 .../src/site/apt/examples/junit-platform.apt.vm          | 16 ++++++++++++----
 1 file changed, 12 insertions(+), 4 deletions(-)

diff --git a/maven-surefire-plugin/src/site/apt/examples/junit-platform.apt.vm b/maven-surefire-plugin/src/site/apt/examples/junit-platform.apt.vm
index 2a86f2a..58741b4 100644
--- a/maven-surefire-plugin/src/site/apt/examples/junit-platform.apt.vm
+++ b/maven-surefire-plugin/src/site/apt/examples/junit-platform.apt.vm
@@ -209,11 +209,12 @@ else
    you can execute <<<mvn -Dtest=org.example.MyTest test>>> from the command line.
 
 
-* Filtering by Test Class Names
+* Filtering by Test Class Names for Maven ${thisPlugin}
 
-   The Maven Surefire Plugin will scan for test classes whose fully qualified names match
+   The Maven ${thisPlugin} Plugin will scan for test classes whose fully qualified names match
    the following patterns.
 
+#{if}(${project.artifactId}=="maven-surefire-plugin")
    * <<<**/Test*.java>>>
 
    * <<<**/*Test.java>>>
@@ -221,14 +222,21 @@ else
    * <<<**/*Tests.java>>>
 
    * <<<**/*TestCase.java>>>
+#{else}
+   * <<<**/IT*.java>>>
+
+   * <<<**/*IT.java>>>
+
+   * <<<**/*ITCase.java>>>
+#{end}
 
    Moreover, it will exclude all nested classes (including static member classes) by default.
 
    Note, however, that you can override this default behavior by configuring explicit
-   `include` and `exclude` rules in your `pom.xml` file. For example, to keep Maven Surefire
+   `include` and `exclude` rules in your `pom.xml` file. For example, to keep Maven ${thisPlugin}
    from excluding static member classes, you can override its exclude rules.
 
-* Overriding exclude rules of Maven Surefire
+* Overriding exclude rules of Maven ${thisPlugin}
 
 +---+
 ...