Hi Greg,
I'm sure you are right, as I read the same on a lot of places over the internet. I have added the log4j-slf4 bridge
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-slf4j-impl</artifactId>
<version>${log4j.version}</version>
</dependency>
in my project but all I can see is slf4j loggings being logged using the slf4j simple logger:
2014-01-13 09:07:07,750 [main] INFO : Mapped "{[/signin/{providerId}],methods=[GET],params=[error],headers=[],consumes=[
],produces=[],custom=[]}" onto public org.springframework.web.servlet.view.RedirectView org.springframework.social.conne
ct.web.ProviderSignInController.oauth2ErrorCallback(java.lang.String,java.lang.String,java.lang.String,java.lang.String,
org.springframework.web.context.request.NativeWebRequest)
[INFO] ResourceChangeScanner reconfigured with interval=60
[INFO] ResourceChangeScanner created with default interval=60
2014-01-13 09:07:08,563 [main] INFO : Root WebApplicationContext: initialization completed in 28985 ms
2014-01-13 09:07:08.564:INFO:/:Log4jServletContextListener ensuring that Log4j starts up properly.
2014-01-13 09:07:08.590:INFO:/:Log4jServletFilter initialized.
[DEBUG] Logging to org.slf4j.impl.SimpleLogger(org.eclipse.jetty.util.log) via org.eclipse.jetty.util.log.Slf4jLog
I believe that someone (jetty, maven, plexus, jetty-maven-plugin) is dragging the slf4j's simple logger in the classpath,
which overrides the log4j2's simplelogger. Unfortunately I can't find out which one.
I will try to create a jetty logger that goes directly to log4j2, cause honestly I don't know what else to do.
