Under some configurations, there are logging conflicts between maven-notifier and build

[Riduidel]

When building with maven 3.2.1 the wisdom framework, I get

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/C:/Program%20Files%20(x86)/Maven/lib/ext/slf4j-nop-1.7.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/C:/Program%20Files%20(x86)/Maven/lib/slf4j-simple-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.helpers.NOPLoggerFactory]

errors at build startup, and not the slightest message is output by maven.
I'm not yet sure if it is maven-notifier's fault but, as it is the one contributing the slf4j-nop-1.7.4.jar, I guess it's a valid suggestion.

[Riduidel]

The fact that the maven build is not related to maven-notifier. However, the fact that maven-notifier generates conflicts is not so good.

[jcgay]

Yep, this is because when using a maven version > 3.1.x, you should not extract slf4j-nop-x.x.x.jar from maven-notifier bundle.
I have recently added the instruction in the installation section, but I will describe the installation for Maven > 3.1.x users in first place for the next version (just download a Uber jar).
The zip package will remain for Maven 3.0.x users and will contain SLF4J api and a binding.

Thanks !