From 32782429afde8744552061496c161427b27eabf7 Mon Sep 17 00:00:00 2001
From: Phillip Webb <pwebb@pivotal.io>
Date: Thu, 29 Mar 2018 17:14:53 -0700
Subject: [PATCH] Attempt to fix server test CI failures

Switch surefire configuration so that forking isn't used. This seems to
prevent the "Corrupted STDOUT by directly writing to native stream"
errors and will hopefully reduce failures on the CI server.

See gh-12689
---
 .../spring-boot-server-tests/pom.xml                           | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/spring-boot-tests/spring-boot-integration-tests/spring-boot-server-tests/pom.xml b/spring-boot-tests/spring-boot-integration-tests/spring-boot-server-tests/pom.xml
index 3cfac345088..a7ad7498267 100644
--- a/spring-boot-tests/spring-boot-integration-tests/spring-boot-server-tests/pom.xml
+++ b/spring-boot-tests/spring-boot-integration-tests/spring-boot-server-tests/pom.xml
@@ -56,6 +56,9 @@
 						<maven.home>${maven.home}</maven.home>
 						<repository>${repository}</repository>
 					</systemPropertyVariables>
+					<useSystemClassLoader>false</useSystemClassLoader>
+					<forkCount>0</forkCount>
+					<reuseForks>false</reuseForks>
 				</configuration>
 			</plugin>
 		</plugins>