title: How to force SLF4J to use logback
body: <p>We have a problem with logging in our application.
  Unfortunatelly we have multiple SLF4J bindings: one is logback (from Play) that we want to use, but in one of our libraries (jar) there is another <code>StaticLoggerBinder.class</code>, which is chosen on a testing machine (locally all works for me...) and as result we have no logs.
  Since we cannot remove the problematic jar from dependencies, is there a way to force the SLF4J to use logback?</p>
  
  <p>In a run script when we specify a location of libs I have noticed, that the order of libs is important. Sorting the dependencies alphabetically instead of pointing to lib/* solves the problem, but the solution is rather unstable... I have tried out <a href="https://stackoverflow.com/a/12521753/4086568">that solution</a>, but my implenetation ended to be the last on the list (from warning printed at startup by SLF4J).</p>
  
  <p>Can somebody help?</p>