leiningen/leiningen-core/project.clj
Toby Crawley 5fd5592711 Force usage of newer dynapath until pomegranate updates.
This fixes the issue causing the build failures. The root of it is
that dynapath was allowing pomegranate to modify the boot classloader,
which caused multiple copies of the same class to be loaded.
2013-02-21 15:04:26 -05:00

22 lines
1.1 KiB
Clojure

(defproject leiningen-core "2.1.0-SNAPSHOT"
:url "https://github.com/technomancy/leiningen"
:license {:name "Eclipse Public License"
:url "http://www.eclipse.org/legal/epl-v10.html"}
:description "Library for core functionality of Leiningen."
:dependencies [[org.clojure/clojure "1.4.0"]
[bultitude "0.1.7" :exclusions [dynapath]]
[classlojure "0.6.6"]
[useful "0.8.6"]
[robert/hooke "1.3.0"]
[com.cemerick/pomegranate "0.0.14-SNAPSHOT" :exclusions [org.tcrawley/dynapath]]
;; depend on this directly until pomegranate upgrades
[org.tcrawley/dynapath "0.2.3"]]
;; until the pomegratate snapshot is released:
:repositories [["sonatype"
"https://oss.sonatype.org/content/repositories/snapshots/"]]
:scm {:dir ".."}
;; This is only used when releasing Leiningen. Can't put it in a
;; profile since it must be installed using lein1
;;:aot :all
:dev-resources-path "dev-resources"
:profiles {:dev {:resource-paths ["dev-resources"]}})