Logback-access logs configuration when app is ran with maven within IDEA

I guess it's an edge case, but it might be useful to understand what's happening (latest IDEA 15 EAP)

This happens with logback configured for a spring-boot based app, with logback-access added to produce access logs.

Here's an excerpt of the stacktrace:


//application startup logback.xml formatted log
2015-09-17 13:31:49.056  INFO 22580 --- [           main] s.b.c.e.t.TomcatEmbeddedServletContainer : Tomcat initialized with port(s): 8080 (http)
//then logback-access init log starts with a different pattern
//13:31:49,711 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - debug attribute not set 13:31:49,714 |-INFO in ch.qos.logback.core.joran.action.StatusListenerAction - Added status listener of type [ch.qos.logback.core.status.OnConsoleStatusListener] ... 13:31:50,070 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - End of configuration. 13:31:50,070 |-INFO in ch.qos.logback.access.joran.JoranConfigurator@5814c52f - Registering current configuration as safe fallback point //
//application startup logback.xml formatted log continues 2015-09-17 13:31:50.138  INFO 22580 --- [ost-startStop-1] com.company.api.userinfo.Application      : Running with Spring profile(s) : [dev]

This log is not controllable, a logger for ch.qos.logback at WARN level doesn't do anything.

This happens when the app is ran with an IDEA Maven configuration. It doesn't happen when the same maven cli is ran with a terminal:
Running the idea commandd with a terminal procudes the same error:

/Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/bin/java -Dmaven.multiModuleProjectDirectory=/Users/nodje/Documents/project/ptmind/ptengine-service -Dmaven.home=/java/apache-maven-3.3.3 -Dclassworlds.conf=/java/apache-maven-3.3.3/bin/m2.conf -Dfile.encoding=UTF-8 -classpath "/java/apache-maven-3.3.3/boot/plexus-classworlds-2.5.2.jar:/Applications/IntelliJ IDEA 15 EAP.app/Contents/lib/idea_rt.jar" org.codehaus.classworlds.Launcher -Didea.version=15.0 -Dspring.profiles.active=test spring-boot:run

This seems to indicate a conflict somewhere in IDEA classes added at runtime.


Please sign in to leave a comment.