leiningen

We have some 3rd-party jars checked-in to our project. We'd like to add them to the classpath. That's it. We don't want to set up a local maven repo (because that would break our 'check out and run' philosophy). Each developer would have to set up their own maven repo, distinct from the project. Is there a way to do this or is this? Most of the answers I've seen say to set up a local maven which we don't want or need just to add a jar to a classpath. You will need to setup a local maven repository, but that can be a simple directory, in your project directory, that you then check in to source

This is the second question after Is there a standalone Clojure package within Leiningen? For example, I have a file hello_world.clj , and I can run it using java -cp clojure.jar clojure.main hello_world.clj . Since lein already contains Clojure (because I can run lein repl directly), is there a way to do the same thing like lein script hello_world.clj by lein? number23_cn use lein-exec plugin, example from readme.md (updated with "lein" instead of "lein2") cat foo.clj | lein exec lein exec -e '(println "foo" (+ 20 30))' lein exec -ep "(use 'foo.bar) (pprint (map baz (range 200)))" lein exec

What I do now is open project.clj, add dependency there, run lein deps restart repl, then use , require and so on. The thing is that I don't really like to restart repl because the startup time is slow and I have to reload my files again. So is there a better way to add dependency to lein project? without restarting the repl? i-blis You can use Alembic , a dynamic classpath loader and dependencies resolver. The good thing is that it doesn't load all pomegranate dependencies. Add the following to your .lein/profiles.clj : {:user {:dependencies [[alembic "0.3.2"]]}} Then in your Repl just load

I'm not sure why but when I enter the REPL through $ clojure or $ lein repl , >(clojure-version) says '1.2.1'. I want it to say '1.5'. Version 1.5 works fine in my projects managed by lein. I just want to tell lein to always use 1.5 by default, instead of 1.2. Currently this isn't supported outside a project, but it's being worked on: https://github.com/technomancy/leiningen/issues/966 A workaround for now is just to specify it in your project.clj Further recommendation: upgrade to Leiningen 2.0. 来源： https://stackoverflow.com/questions/15170388/how-to-change-clojure-or-leins-clojure-default

Does anyone know why I'm getting the below error? I read through answers of similar questions, which recommended using Leiningen, which I've done below and still get the error. MacBook-Pro:~ xxx$ lein new app test Generating a project called test based on the 'app' template. MacBook-Pro:~ xxx$ cd test MacBook-Pro:test xxx$ lein repl nREPL server started on port 59623 on host 127.0.0.1 REPL-y 0.2.1 Clojure 1.5.1 Docs: (doc function-name-here) (find-doc "part-of-name-here") Source: (source function-name-here) Javadoc: (javadoc java-object-or-class-here) Exit: Control+D or (exit) or (quit)

I realize that this question is pretty much the exact question found here . However, seeing as that question is 1.5 years old (or so), I would like to revisit it. How does one add local dependencies using leiningen? Surely this capability must exist by now? Create a private Maven Repository , and then, add the following to your project.clj :repositories {"local" ~(str (.toURI (java.io.File. "your_local_repository")))} If the jars are based on your own projects, you can use lein install to put them into your local .m2, or use the checkout-dependencies feature. You can also use the extra

I want to be able to query or embed the version string set by the leiningen project and display that value to user. Uses include displaying the version string from the CLI, or as a header in a ring application. Is this possible? If you're running inside Leiningen using lein run or the like, it's available as a system property: (System/getProperty "myproject.version") . If you're producing a jar you need to read pom.properties . I like technomancy's answer, but I had to go look up how to "read pom.properties ". It turns out that for the maven artifact com.example/my-project, there is a file on