@Andy: we support for some time the user selection by simply providing in the app slf4j api + impl of the app choice
that's why i asked how it was started, it embedded mode (i guess that's the case) the user can simply exclude the binding which doesnt match his need so basically it should all be fine *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/5/15 AndyG <[email protected]> > A quick fix would be removing, renaming or replacing the > slf4j-jdk14-1.7.2.jar with the logback-classic-1.0.11.jar. Also ensure you > have logback-core-1.0.11.jar on the classpath. > > Really we shouldn't be shipping slf4j-jdk14 or any other binding in the > tomee/lib directory (http://slf4j.org/faq.html#requirements). This will > allow the user to drop in their own choice if/when slf4j is enabled. > > Andy. > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/slf4j-jdk14-1-7-2-jar-overrides-logback-tp4662958p4662969.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
