If you carefully read the error messge provided, you will notice that your problem is multiple bindings of sfl4j on your build path. You included sfl4j-log4j and logback-classic artifacts. Since logback-classic already contains native implementation of sfl4j and also automatically adds sfl4j jar to your project you end up having mutiple sf4j's in your build path. Simply make up your mind and choose only one logging framework and remove another one from your dependencies.
So if you choose logback-classic your Maven dependencies will look like this:
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
<version>1.1.1</version>
</dependency>
If you choose log4j then make it look like this
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>1.7.2</version>
</dependency>
But don't include both!
From sfl4j manual:
If you wish to use logback-classic as the underlying logging framework, all you need to do is to declare "ch.qos.logback:logback-classic" as a dependency in your pom.xml file as shown below. In addition to logback-classic-1.0.13.jar, this will pull slf4j-api-1.7.7.jar as well as logback-core-1.0.13.jar into your project. Note that explicitly declaring a dependency on logback-core-1.0.13 or slf4j-api-1.7.7.jar is not wrong and may be necessary to impose the correct version of said artifacts by virtue of Maven's "nearest definition" dependency mediation rule