Error added: 2011-07-19T08:32:47Z
Gaaad. What is it about the authors of logging libraries? They think that everyone cares about their bindings, interfaces, and stuff - WE DON'T. We just want a single, good implementation that we can use. We're likely not going to want to swap logging systems half-way through a project. Grrr.
See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
This error is reported when the org.slf4j.impl.StaticLoggerBinder class could not be loaded into memory. This happens when no appropriate SLF4J binding could be found on the class path. Placing one (and only one) of slf4j-nop.jar, slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or logback-classic.jar on the class path should solve the problem. As of SLF4J version 1.6, in the absence of a binding, SLF4J will default to a no-operation (NOP) logger implementation. You can download SLF4J bindings from the project download page.
If you know the answer, please add your own solution below.
If you don't know, but find out later, please come back and share your answer - there will be other people
struggling with this too.
If you want to be notified via email when this is solved, enter your email address here: