Integration tests: turn on debugging in Karaf log

This patchs turns on karaf debug output for integration tests for all
lispflowmapping classes, not just the MappingServiceIntegrationTest
class itself. This is extremely valuable when debugging integration
tests issues, both on a local build, or in Jenkins. The karaf log for
the integration tests can be found in the
integrationtest/target/surefire-reports/org.opendaylight.lispflowmapping.integrationtest.MappingServiceIntegrationTest-output.txt
file, and with this patch it will have full debug output. If trace level
output is needed, the next line can be changed too, but that's overkill
for most situations, and should be used at a developer's discretion, but
not by default in the build.

Change-Id: Ice723eac5509706e8b633bab5aa02d83758855fd
Signed-off-by: Lorand Jakab <lojakab@cisco.com>

diff --git a/integrationtest/src/test/java/org/opendaylight/lispflowmapping/integrationtest/MappingServiceIntegrationTest.java b/integrationtest/src/test/java/org/opendaylight/lispflowmapping/integrationtest/MappingServiceIntegrationTest.java
index 44e7935b7398abdb25f43aa651da5dd9bf0e6937..1a6b9f5a1e41204b7c8ae0762137a73c53312352 100644 (file)
--- a/integrationtest/src/test/java/org/opendaylight/lispflowmapping/integrationtest/MappingServiceIntegrationTest.java
+++ b/integrationtest/src/test/java/org/opendaylight/lispflowmapping/integrationtest/MappingServiceIntegrationTest.java
@@ -177,7 +177,7 @@ public class MappingServiceIntegrationTest extends AbstractMdsalTestBase {
     @Override
     public Option getLoggingOption() {
         Option option = editConfigurationFilePut(ORG_OPS4J_PAX_LOGGING_CFG,
-                logConfiguration(MappingServiceIntegrationTest.class),
+                "log4j.logger.org.opendaylight.lispflowmapping",
                 LogLevel.DEBUG.name());
         option = composite(option, super.getLoggingOption());
         return option;