Use SLF4J instead of Log4j about wiremock

[tomakehurst]

True, and it's on the list.

You can however write your own Notifier impl for the same effect.

[williamvoor]

Somehow related to this issue. I tried to decrease log levels of wiremock to ERROR only, and it appears loggers are created with under multiple names, not following a package hierarchy. To achieve the ERROR level I had to include 4 logger names in my log4j.xml (com.github.tomakehurst.wiremock, /__admin, /, org.mortbay.log). Is this an intended behaviour?

[tomakehurst]

Sort of. I originally set the loggers up with only the standalone use case in mind. This wasn't a great decision, and it's one I intend to revisit at some point.

[o-nix]

Vote for such refactoring. Otherwise I'm forced to add log4.properties.

[yogurtearl]

+1 for this. I think it would help with running WireMock on Android.

[tomakehurst]

One caveat with this - there has to be a logging impl in the standalone JAR (and I'm minded to keep log4j for that), so it'll only be possible to switch logging implementations when using the non-standalone JAR.

Does this still solve everyone's issues?

Can anyone think of a better way?

[williamvoor]

Sounds good. I believe people using standalone would not care what logger is being used.

[xunnanxu]

You could include slf4j, log4j, and the binding in the dependency. So if a project needs to use something else, we can just exclude log4j and its binding.

[tomakehurst]

Please see/comment on:
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/wiremock-user/a6Reo7QAMYo/rzY5v8Apgv8J

[tomakehurst]

This is done on master now. Release shortly.

[xunnanxu]

kudos for the banner but wonder how many people would like that

[tomakehurst]

You think some people might object to it? Any particular reason?