• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1619
  • Last Modified:

Eclipse - Kepler Maven slf4j annoyance

While not critical this error has me  stumped. I already tried the jar files suggested in the hyperlink but the error persists.  Any ideas how to truly resolve this?
given
Eclipse Kepler release 2
eclipse m2e plugins version  1.4.x
Here is the output:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
[INFO] Scanning for projects...
[INFO]                                                                        
[INFO] ------------------------------------------------------------------------
[INFO] XYZ Project  1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-cli) @ XYZ Project ---
[INFO] Nothing to compile - all classes are up to date
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.350s
[INFO] Finished at: Thu Apr 03 09:32:48 EDT 2014
[INFO] Final Memory: 9M/244M
[INFO] ------------------------------------------------------------------------
0
Robert Silver
Asked:
Robert Silver
1 Solution
 
chaitu chaituCommented:
this issue is reported in http://www.slf4j.org/codes.html site.

This is the solution they have given..

Failedto load class org.slf4j.impl.StaticLoggerBinder

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.
SINCE 1.6.0 As of SLF4J version 1.6, in the absence of a binding, SLF4J will default to a no-operation (NOP) logger implementation.
0
 
Robert SilverSr. Software EngineerAuthor Commented:
I will try it but I am not currently running it as a web application rather I am just building the project with Maven under goal   of compiler:compile. No Tomcat yet although it probably is a dependency library
0

Featured Post

The Firewall Audit Checklist

Preparing for a firewall audit today is almost impossible.
AlgoSec, together with some of the largest global organizations and auditors, has created a checklist to follow when preparing for your firewall audit. Simplify risk mitigation while staying compliant all of the time!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now