Oups, I'll look at it... we may have well upgraded Lein without reviewing project.clj options. We're about to deliver another version of our software so it's just about time to do that.
On Tue, 22 Nov 2011 10:57:47 -0800 Phil Hagelberg <p...@hagelb.org> wrote: > On Mon, Nov 21, 2011 at 9:10 PM, Keith Irwin <keith.ir...@gmail.com> > wrote: > > 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? > > This is just a quirk of the Clojure compiler; there's currently no way > to compile a namespace without compiling all its dependencies: > http://dev.clojure.org/jira/browse/CLJ-322 > > Leiningen includes a workaround for this; you can set > :clean-non-project-classes in project.clj, but it's not on by default > since there are edge cases with protocols where it breaks. The option > Luc mentioned is from an older version where it was turned on by > default. > > It's best to avoid AOT compilation unless you need it. You can use the > -m option to lein run to avoid having to declare your -main namespaces > in project.clj: > > $ lein run -m clojure.main > > -Phil > -- 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
