I have the same problem: I copied my POM into an empty project and reduced it to almost nothing (see below) - and I still see the error. I can confirm that it does not go away by adding SLF4J bindings (logback, etc.) to the POM - the message apparently comes from Maven itself, and not from compiling and testing the project software. (Now I get it from a completely empty project.)
The best thing I can understand is that I think it has something to do with Eclipse: when I start Maven manually, the error does not appear from the command line - only when called in Eclipse. (I use Eclipse Helios Release 2 on MacOSX, just FYI, so we know the problem is not limited to your version, Juno.)
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>testing</groupId> <artifactId>testing</artifactId> <version>0.0.1-SNAPSHOT</version> </project>
FYI, in response to Ceki's suggestion, here are the results of the maven dependency tree tree:
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
Not too informative, but it is.
Tim
source share