On Dec 18, 4:16 am, Roman Roelofsen <roman.roelof...@googlemail.com> wrote: > IMHO, no. This is the whole problem. Library users will mostly care > about the runtime. It doesn't help at all if your code compiles, maybe > in isolated pieces, but everything blows up at runtime. For example, I > never had problems compiling against the correct Log4j version. Maven > will set up the classpath for each "compiliation unit" (here Maven > module) individually. But I stopped counting how often the runtime > screw up because several libraries were using log4j, all expecting > different version, and the whole classpath was a total mess of > different jar files, redundancy and shadowed classes. > > Solving this problem at runtime implies a solution for build time but > not the other way around.
Thanks for the explanation, I still have lots of learning to do on this subject. > I am looking at this constantly :-) I am working on an intergration > layer (http://wiki.github.com/romanroe/ogee) but I haven't had much > time in the last weeks. Ogee also has a small context-oriented > programming module and I am focusing on this anyway currently. I hope your project work out fine, it would certainly be a nice addition to Clojure for managing that kind of situation. I'll give it a closer look when I'll have more time on my hands. - budu -- 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
