Thanks Phil, the release jars address my concerns. Just to elaborate on Sean C's post, I think Leiningen is a great initiative - especially for those new to clojure/java, but for me it and maven are dissonant with my setup. From various comments on the list, I suspect there are others who have a similar view.
My particular perspective is; - A long-time Java (Unix) developer who has evolved a rich set of home-grown bash/ant processes for managing dev, test and a number of production servers. - Two-odd years of clojure dev and "melding" that into the above environment - A personal antipathy towards "bloat" and anything that "just gets downloaded" without my fully understanding what it is and why it's there. - A willingness to deal with sorting out dependencies myself. - The above in order to have full control and transparency over an environment in which I have full accountability to a demanding and unforgiving customer base. For me, the ideal is having a set of stable jars from release to release for both clojure and c.c and those third party libs which I use. I am happy with the modularization of c.c as I can "meld" those as well and get a more refined subset. I have no problem bashing (yeah pun) together a utility to build my own c.c jar from the distribution or from github for experimental dev. I simply appeal to other third-party library developers to structure their (preferably github) source so that dependencies are easy to separate out and handle ourselves. - Adrian. On Thu, Sep 9, 2010 at 7:03 AM, Sean Corfield <seancorfi...@gmail.com> wrote: > I think Leiningen does a great job of hiding maven. I initially wanted > to avoid Leiningen because of maven and when I was putting together > cfmljure (as a way to introduce Clojure to CFML developers :) I > initially documented the download ZIP, unzip, copy JARs approach but > then I reconsidered and updated cfmljure to work better with Leiningen > projects and updated the docs for lein instead. I think it's by far > the easiest way to deal with getting Clojure up and running. You > download one script, make it executable and run it to install > Leiningen and then projects are as easy as 1. lein new myproject, 2. > lein deps, 3. lein test - although I pretty much always add lein-run > and I'm looking forward to it being built into Leiningen at some > future date (hopefully!). > > On Wed, Sep 8, 2010 at 8:38 PM, Adrian Cuthbertson > <adrian.cuthbert...@gmail.com> wrote: >> I strongly support any initiative that does not assume maven is a given. >> >> -Rgds, Adrian. >> >> On Thu, Sep 9, 2010 at 5:03 AM, Sean Devlin <francoisdev...@gmail.com> wrote: >>> Until you don't want to deal with maven, and just need a jar. Like if >>> you're installing Enclojure & just want the stupid jars. > > -- > 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 -- 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
