On Sun, Apr 25, 2010 at 1:17 PM, Allen Johnson <akjohnso...@gmail.com>wrote:
> > What seems to be happening is that when I build my 'gen-class' package, > the > > class is nailed down even though logging.clj itself is not gen-classed. > > I'm not familiar with GAE but as a workaround can you include the > commons-logging.jar in your war file? Then configure commons-logging > to delegate to java.util.logging. > > Thanks for the help and suggestion. Yes, though as I mentioned it is a more general problem than this particular case. I have gone through the patch of c.c.logging which now changed to use 'eval' to delay the loading(thus should solve the nailed down too early issue). This seems like a DI injection equivalent. The problem of shipping the commons-logging.jar is that I am getting into the the app container turf(say in the case they have their own google.logging). What if say I am using the JPA/JDO where my development environment is mysql and the runtime is something else ? In other words, all this 'try import ...' tricks should(?) be done in the latest patched way of using eval as there can be multiple build points along the path (the clojure-contrib build, my own build, could be some more build if I write a wrapper which also use c.c.logging and someone takes my wrapper, just like c.c.logging, then the final runtime). Just not sure what form of performance impact it carries(not that I care for this particular case). -- 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
