[SUREFIRE-1975] JDK18 - The Security Manager is deprecated and will b…

…e removed in a future release
apache · Jan 1, 2022 · ba44457 · ba44457
1 parent e4d67a5
commit ba44457
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/maven-surefire-plugin/src/site/apt/examples/junit.apt.vm b/maven-surefire-plugin/src/site/apt/examples/junit.apt.vm
@@ -203,6 +203,8 @@ else
 
    As long as <<<forkCount>>> is not 0 and you use JUnit3, you can run your tests with a Java security manager enabled.
    The class name of the security manager must be sent as a system property variable to the JUnit3 provider.
+   The JDK 17 deprecated the class <<<java.lang.SecurityManager>>> and the JUnit3 provider fails with enabled system
+   property <<surefire.security.manager>>>.
 
    JUnit4 uses mechanisms internally that are not compatible with the tested
    security managers and thus this means of configuring a security manager with JUnit4 is not supported