+1, looks like a good switch. -Nick
Nicholas Gallardo WebSphere - REST & WebServices Development [email protected] Phone: 512-286-6258 Building: 903 / 5G-016 "Snitkovsky, Martin" <martin.snitkovsk To [email protected]> "[email protected]" <[email protected]> 06/25/2009 03:45 cc AM Subject RE: Commons-logging -> SLF4J Please respond to wink-...@incubato r.apache.org Hi Jason, After doing some research (didn't have any previous experience with SLF4J), I am in favor of switching to SLF4J - more simple, no class loader magic, no dynamic binding, support for {}-placeholders +1 -----Original Message----- From: Jason Dillon [mailto:[email protected]] On Behalf Of Jason Dillon Sent: Wednesday, June 24, 2009 6:42 PM To: [email protected] Subject: Commons-logging -> SLF4J I would like to move the logging framework from Commons-logging to SLF4J. SLF4J has less classloading wrinkles than JCL and has a smaller foot print, while providing more logging features, most significantly its fast parser for "{}" replacement which makes the need for most if (log.isDebugEnabled()) {} blocks uneeded. If there are no objections I would like to provide a patch to move from JCL to SLF4J. --jason
