[maven-surefire] 02/02: [developing.apt.vm] development documentation renamed JDK 1.6 to JDK 1.7

[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

commit e6fb1989ab42fc0562209330e9d5eb92c326645e
Author: Tibor17 <ti...@apache.org>
AuthorDate: Wed Dec 19 07:24:42 2018 +0100

    [developing.apt.vm] development documentation renamed JDK 1.6 to JDK 1.7
---
 maven-surefire-plugin/src/site/apt/developing.apt.vm | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/maven-surefire-plugin/src/site/apt/developing.apt.vm b/maven-surefire-plugin/src/site/apt/developing.apt.vm
index 680201a..7299b9a 100644
--- a/maven-surefire-plugin/src/site/apt/developing.apt.vm
+++ b/maven-surefire-plugin/src/site/apt/developing.apt.vm
@@ -114,9 +114,12 @@ ForkedBooter#main
 
 * JDK Versions
 
-  The surefire booter is capable of booting all the way back to jdk1.6. Specifically
-  this means <<<surefire-api>>>, <<<surefire-booter>>>, <<<common-junit3>>> and <<<surefire-junit3>>> are
-  source/target 1.6. The plugin and several providers are 1.6.
+  The surefire booter is capable of booting all the way back to jdk1.7. Specifically
+  this means <<<surefire-api>>>, <<<surefire-booter>>>, <<<common-junit3>>>, <<<surefire-junit3>>>
+  and other modules are compiled with source/target 1.7. The plugin and several providers are 1.7.
+  The provider <<<surefire-junit-platform>>> is compiled with jdk1.8.
+  The project requires using <<<JAVA_HOME>>> jdk1.8 but the tests run with jdk1.7+ which is
+  configured by system property <<<jdk.home>>>, see <<<README.md>>>.
 
 * Provider Isolation