+1 here too. See also log4j-over-slf4j<http://search.maven.org/#artifactdetails%7Corg.slf4j%7Clog4j-over-slf4j%7C1.7.2%7Cjar> for interop until the port is complete or for users that need to use older versions. There's also jcl-over-slf4j<http://search.maven.org/#artifactdetails%7Corg.slf4j%7Cjcl-over-slf4j%7C1.7.2%7Cjar> (Jakarta Commons Logging over SLF4J) & jul-to-slf4j<http://search.maven.org/#artifactdetails%7Corg.slf4j%7Cjul-to-slf4j%7C1.7.2%7Cjar>(java.util.Logging to SLF4J).
I use (read: express a dependency on) logback-classic<http://search.maven.org/#artifactdetails%7Cch.qos.logback%7Clogback-classic%7C1.0.9%7Cjar>in my projects, then exclude commons-logging & log4j from any dependencies and add jcl-over-slf4j & log4j-over-slf4j, respectively. On Thu, Jan 31, 2013 at 5:26 AM, Martin Grigorov <[email protected]>wrote: > Hi, > > As a user of Logback I prefer if the libraries/frameworks I need to use a > logging facade. > slf4j is the best in the market at the moment. > > Here is my +1 > > > On Thu, Jan 31, 2013 at 12:15 PM, Dan Haywood > <[email protected]>wrote: > > > ... my vote would be yes. for more on the libraries, see [1] and [2]. > > the executive summary as to why slf4j can be found at bottom of [3] > > > > There's apparently a migrator tool [4]. I'd be happy to do the grunt > work > > for core, jdo, wicket, restful and shiro (ie the components currently > > released as 1.0.0 or greater) > > > > Opinions? > > > > [1] http://logging.apache.org/ > > [2] http://www.slf4j.org/ > > [3] http://www.slf4j.org/manual.html > > [4] http://www.slf4j.org/migrator.html > > > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com <http://jweekend.com/> > -- mailto:[email protected] <[email protected]> skype:matthewadams12 googletalk:[email protected] http://matthewadams.me http://www.linkedin.com/in/matthewadams
