[maven-surefire] branch master updated: mentioning JUnit5 in usages.apt.vm

[t***@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 fdebc82 mentioning JUnit5 in usages.apt.vm
fdebc82 is described below

commit fdebc82ab685b1a4b72ff88fd3a70f59b02426cd
Author: Tibor17 <***@apache.org>
AuthorDate: Mon Dec 10 03:59:58 2018 +0100

mentioning JUnit5 in usages.apt.vm
---
maven-surefire-plugin/src/site/apt/usage.apt.vm | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/maven-surefire-plugin/src/site/apt/usage.apt.vm b/maven-surefire-plugin/src/site/apt/usage.apt.vm
index c442e67..6b7e706 100644
--- a/maven-surefire-plugin/src/site/apt/usage.apt.vm
+++ b/maven-surefire-plugin/src/site/apt/usage.apt.vm
@@ -104,14 +104,14 @@ mvn verify

* TestNG

- * JUnit (3.8 or 4.x)
+ * JUnit (3.8, 4.x or 5.x)

* POJO

Which providers are available is controlled simply by the inclusion of the
- appropriate dependencies (i.e., <<<junit:junit>>> or <<<junit:junit-dep>>> for JUnit and <<<org.testng:testng>>> 4.7+
- for TestNG). Since this is required to compile the test classes anyway, no
- additional configuration is required.
+ appropriate dependencies (i.e., <<<junit:junit>>> or <<<junit:junit-dep>>> for JUnit4, <<junit-jupiter-engine>> or
+ <<junit-vintage-engine>> for JUnit5 and <<<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