I agree with Meikel on this one. Java isn't the best language, but they figured out how to package code in a way that makes it easy to reuse - the JAR. Maven may not be the easiest thing in the world to work with, but they got dependency management right.
clojure-contrib should probably be broken up eventually. Some pieces could arguably be brought into core. Other pieces are obviously half- baked (I won't name names) and should be pulled into separate projects so that they can be dynamic and alive, rather than a slave to a monolithic release cycle. It would be nice to have a single place you could go to find/search Clojure libraries... that way you don't rely on clojure-contrib to be the *only* source of reusable Clojure code in the known universe. :-) Oh, hey, what about http://clojure.org/libraries ? On May 24, 11:40 pm, Meikel Brandmeyer <m...@kotka.de> wrote: > Hi, > > On May 25, 2:33 am, Stuart Halloway <stuart.hallo...@gmail.com> wrote: > > > How can we get both? > > By providing a non-monolithic build? Once upon a time, I did > this in a non-intrusive way using Ivy[1]. Back then the interest > was close to zero. Now that contrib uses maven, this should be > a non-brainer, no? Create a subproject for each logical module. > People can depend on fine-grained modules. The modules may > (but don't have to) do releases independently from each other. > > Sincerely > Meikel -- 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
