Hi, Do you have the :disable-implicit-clean option set to false in your project.clj file ? If not, add it to remove the classes from dependencies that otherwise may pollute your target.
As far as "standard" logging in a lib, it might be time to rely on clojure.tools.logging systematically. We do not use it here yet but at some point it will become unavoidable. Luc P. On Mon, 21 Nov 2011 21:10:31 -0800 (PST) Keith Irwin <keith.ir...@gmail.com> wrote: > Folks-- > > I'm working on an experimental library which interfaces with external > resources (i.e., not purely functional) and I'd like the library to > log things when stuff goes wrong (say, with network connections). I > don't want to throw exceptions and let clients handle it because I > want to build in some automated reconnect stuff. > > Normally, I use clojure.tools.logging and add dependencies for log > back. Works great. > > What's the standard way for including logging in a library? I've > included clojure.tools.logging as a dependency, but the resulting jar > (lein install), contains clojure.tools.logging classes. Is that okay, > given any project its likely to be included in will also depend on > clojure.tools.logging? > > Is there some way to do this? Is embedded logging (like Jetty has, > for instance), just Not Done in the clojure library world? > > Keith > -- Luc P. ================ The rabid Muppet -- 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
