You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
5765cfe010
Previously, when RunProcess handled a SIGINT it would immediately attempt to destroy the process that it had run. This created a race condition between the SIGINT being handled by the child process and RunProcess destroying the child. The exact behavior of destroy is implementation dependent and it may result in forcible termination of the process where shutdown hooks are not called. This is what happens on Windows. The exit code in such a case is 1 which prevents anything from waiting for the process to complete from detecting that it ended as a result of a SIGINT, leaving it with no choice but to report an error. This is what happens with mvn spring-boot:run with a forked process on Windows and results in the build failing. This commit updates RunProcess to allow the child process to handle the SIGINT itself, waiting for up to five seconds for that to happen before the process is then destroyed. Given this time, the child process exits with 130 which RunMojo already handles correctly as indicating that the process died due to SIGINT and the build completes with success as a result. Fixes gh-18936 |
5 years ago | |
|---|---|---|
| .. | ||
| spring-boot-antlib | 5 years ago | |
| spring-boot-autoconfigure-processor | 5 years ago | |
| spring-boot-configuration-metadata | 5 years ago | |
| spring-boot-configuration-processor | 5 years ago | |
| spring-boot-gradle-plugin | 5 years ago | |
| spring-boot-loader | 5 years ago | |
| spring-boot-loader-tools | 5 years ago | |
| spring-boot-maven-plugin | 5 years ago | |
| spring-boot-test-support | 5 years ago | |
| pom.xml | 5 years ago | |