Re:Why we are choosing Clojure as our main programming language
by gislik on Monday March 21, 2011 @01:34PM
(#2350695)
ouch ... formatting is clearly not preserved :(
But take a look at https://github.com/technomancy/leiningen
Re:Why we are choosing Clojure as our main programming language
by dpritchett on Monday March 21, 2011 @01:53PM
(#2350798)
(defproject leiningen "1.5.0-RC1"
:description "A build tool designed not to set your hair on fire."
:url "https://github.com/technomancy/leiningen"
:license {:name "Eclipse Public License"}
:dependencies [[org.clojure/clojure "1.2.0"]
[org.clojure/clojure-contrib "1.2.0"]
[lancet "1.0.0"]
[jline "0.9.94"]
[robert/hooke "1.1.0"]
[org.apache.maven/maven-ant-tasks "2.0.10" :exclusions [ant]]]
:disable-implicit-clean true
:eval-in-leiningen true)
Re:Why we are choosing Clojure as our main programming language
by cdavid on Monday March 21, 2011 @10:51PM
(#2352830)
I am not familiar with leiningen or clojure, but it looks like you are just adding a list of requirements + version, which is exactly what you get with pip + requirements.txt file ?
Re:Why we are choosing Clojure as our main programming language
by dpritchett on Tuesday March 22, 2011 @10:15AM
(#2354413)
I believe that's what's going on, yes. Leiningen runs on top of Maven and so it's downloading the jars you need and storing them in ~/.m2/ where they will be linked in at compile time.
A "lein uberjar" will roll your whole program up into one .jar file, ready for deployment.
A typical deployment instruction file (project.clj) looks like this and with "lein deps" you're all set up in a few seconds.
(defproject leiningen "0.5.0-SNAPSHOT" :description "A build tool designed to not set your hair on fire." :url "http://github.com/technomancy/leiningen :dependencies [[org.clojure/clojure "1.1.0"] [org.clojure/clojure-contrib "1.1.0"]] :dev-dependencies [[swank-clojure "1.2.1"]])