HSEARCH-3151 Fix logging configuration that was being ignored in OSGi…

… tests
hibernate · Sep 24, 2018 · 6628db0 · 6628db0
1 parent f94bdde
commit 6628db0
Showing 1 changed file with 7 additions and 2 deletions.
diff --git a/.../src/test/java/org/hibernate/search/test/integration/osgi/HibernateSearchWithKarafIT.java b/.../src/test/java/org/hibernate/search/test/integration/osgi/HibernateSearchWithKarafIT.java
@@ -172,10 +172,15 @@ public Option[] config() throws IOException {
 						"rmiRegistryHost", "127.0.0.1"
 				),
 				// set the log level for the in container logging to INFO
-				// also just logging to file (out), check data/log/karaf.log w/i the Karaf installation for the test execution log
 				editConfigurationFilePut(
 						"etc/org.ops4j.pax.logging.cfg",
-						"log4j.rootLogger", "INFO, out"
+						"log4j2.rootLogger.level", "INFO"
+				),
+				// also log to the console, so that failsafe can capture the logs in the test output file
+				editConfigurationFilePut(
+						"etc/org.ops4j.pax.logging.cfg",
+						"log4j2.rootLogger.appenderRef.Console.filter.threshold.level",
+						"TRACE" // Means "whatever the root logger level is"
 				),
 				/*
 				 * Use the same local Maven repository as the build job.