Yeah, the fix-patch was submitted prior to the final release of 1.1.0, but alas none of those with the power to actually commit the patch got around to it until it was too late.
On Apr 25, 3:40 pm, gary ng <garyng2...@gmail.com> wrote: > On Sun, Apr 25, 2010 at 3:34 PM, ataggart <alex.tagg...@gmail.com> wrote: > > Was the problem you're having occurring with the latest version of > > cc.logging (the one that uses eval)? > > > The logging macros do not emit calls to the logging implementation, > > but rather to c.c.logging functions that are implemented at runtime > > via eval. As such, the latest code should always pick an > > implementation based on the runtime classpath, thus the environment in > > which AOT compilation takes place should have no effect. > > > While I'm not sure how it could happen, this may end up being a > > classloader problem. > > No. it was an older version packaged with enclojure(not the eval version). I > need to download clojure-contrib and build my own version in order to try > that out. > > That although may present other issue as I don't know if the head version of > clojure-contrib has any dependency on head version of clojure(i.e. 1.2.0). > > -- > 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 > athttp://groups.google.com/group/clojure?hl=en -- 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
