You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by ti...@apache.org on 2019/07/24 15:51:46 UTC
[maven-surefire] 01/01: [SUREFIRE-1682] Default value for config
parameter 'shutdown' should change from 'testset' to 'exit'
This is an automated email from the ASF dual-hosted git repository.
tibordigana pushed a commit to branch SUREFIRE-1682
in repository https://gitbox.apache.org/repos/asf/maven-surefire.git
commit 73f6fc6f7716800232969e50d78b56ed0ff8d374
Author: tibordigana <ti...@apache.org>
AuthorDate: Wed Jul 24 17:51:28 2019 +0200
[SUREFIRE-1682] Default value for config parameter 'shutdown' should change from 'testset' to 'exit'
---
.../org/apache/maven/plugin/failsafe/IntegrationTestMojo.java | 9 +++++----
.../java/org/apache/maven/plugin/surefire/SurefirePlugin.java | 9 +++++----
2 files changed, 10 insertions(+), 8 deletions(-)
diff --git a/maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/IntegrationTestMojo.java b/maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/IntegrationTestMojo.java
index e2bf188..d900e37 100644
--- a/maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/IntegrationTestMojo.java
+++ b/maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/IntegrationTestMojo.java
@@ -359,10 +359,11 @@ public class IntegrationTestMojo
* After the plugin process is shutdown by sending <i>SIGTERM signal (CTRL+C)</i>, <i>SHUTDOWN command</i> is
* received by every forked JVM.
* <br>
- * By default ({@code shutdown=testset}) forked JVM would not continue with new test which means that
- * the current test may still continue to run.
+ * The value is set to ({@code shutdown=exit}) by default (changed in version 3.0.0-M4).
* <br>
- * The parameter can be configured with other two values {@code exit} and {@code kill}.
+ * The parameter can be configured with other two values {@code testset} and {@code kill}.
+ * <br>
+ * With({@code shutdown=testset}) the test set may still continue to run in forked JVM.
* <br>
* Using {@code exit} forked JVM executes {@code System.exit(1)} after the plugin process has received
* <i>SIGTERM signal</i>.
@@ -371,7 +372,7 @@ public class IntegrationTestMojo
*
* @since 2.19
*/
- @Parameter( property = "failsafe.shutdown", defaultValue = "testset" )
+ @Parameter( property = "failsafe.shutdown", defaultValue = "exit" )
private String shutdown;
/**
diff --git a/maven-surefire-plugin/src/main/java/org/apache/maven/plugin/surefire/SurefirePlugin.java b/maven-surefire-plugin/src/main/java/org/apache/maven/plugin/surefire/SurefirePlugin.java
index e23f05e..37bf3cf 100644
--- a/maven-surefire-plugin/src/main/java/org/apache/maven/plugin/surefire/SurefirePlugin.java
+++ b/maven-surefire-plugin/src/main/java/org/apache/maven/plugin/surefire/SurefirePlugin.java
@@ -338,10 +338,11 @@ public class SurefirePlugin
* After the plugin process is shutdown by sending <i>SIGTERM signal (CTRL+C)</i>, <i>SHUTDOWN command</i> is
* received by every forked JVM.
* <br>
- * By default ({@code shutdown=testset}) forked JVM would not continue with new test which means that
- * the current test may still continue to run.
+ * The value is set to ({@code shutdown=exit}) by default (changed in version 3.0.0-M4).
* <br>
- * The parameter can be configured with other two values {@code exit} and {@code kill}.
+ * The parameter can be configured with other two values {@code testset} and {@code kill}.
+ * <br>
+ * With({@code shutdown=testset}) the test set may still continue to run in forked JVM.
* <br>
* Using {@code exit} forked JVM executes {@code System.exit(1)} after the plugin process has received
* <i>SIGTERM signal</i>.
@@ -350,7 +351,7 @@ public class SurefirePlugin
*
* @since 2.19
*/
- @Parameter( property = "surefire.shutdown", defaultValue = "testset" )
+ @Parameter( property = "surefire.shutdown", defaultValue = "exit" )
private String shutdown;
/**