3 ms·
(defproject leiningen "1.5.0-RC1" :description "A build tool designed not to set your hair on fire." :url "https://github.com/technomancy/leiningen"
by dpritchett 16y ago
(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)
- cdavid 16y agoI 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 ?
- dpritchett 16y agoI 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.