On Jan 12, 10:52 pm, Baishampayan Ghose <b.gh...@ocricket.com> wrote: > On Tuesday 12 January 2010 07:30 PM, Shantanu Kumar wrote: > > > This behaviour might occur due to an old Apache Commons-Logging JAR, > > several of which have had classpath / class-loading issues. Just a > > thought. > > Which is the recommended latest version of log4j? As I can see, 2.0 is > too experimental and 1.3 has been made obsolete. > > I tried using 1.2.14 because 1.2.15 was bringing in a truck load of > dependencies.
The following combo has worked fine for me in dev and production: Commons Logging - 1.1.1 (it uses Log4j or java.util.logging as underlying implementation) Log4j - 1.2.14 If it doesn't work for you with c.c.logging, then i'd suggest you try using Commons-Logging directly. Regards, Shantanu
-- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
