We are speaking of two different things.

SLF4J is a facade, like commons-logging (and to some extent
c.c.logging). Their intent is to allow *libraries* to make logging
calls, but leave the actual logging implementation up to the runtime
application.  This in principle allows multiple libraries' log
messages to get routed using whatever implementation the ultimate
application wishes.  If you're the only one that's ever going to run
your code, then writing java calls directly to log4j is fine, though
doing that in clojure is a bit of a hassle, hence c.c.logging
benefitting from delayed evaluation, etc.

My earlier comment about log4j was in terms of what actually gets
configured to do the work of logging messages.



On Sep 15, 5:10 pm, Daniel Simms <daniel.si...@gmail.com> wrote:
> On Wed, Sep 15, 2010 at 12:23 PM, ataggart <alex.tagg...@gmail.com> wrote:
> > If you really need logging, then log4j is probably your best bet
> > anyway.
>
> Or SLF4J, which seems to be the way many (most?) java libraries depend
> on a some logging library.

-- 
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

Reply via email to