Browse files

Apply feedback from Steve Losh on tutorial.

  • Loading branch information...
technomancy committed May 24, 2012
1 parent 14f566b commit cd9a4960020d5ec94f30a0a80a4a69089fd80b6d
Showing with 130 additions and 198 deletions.
  1. +13 −1 doc/
  2. +88 −192 doc/
  3. +7 −1 src/leiningen/compile.clj
  4. +6 −2 src/leiningen/javac.clj
  5. +16 −2 src/leiningen/test.clj
@@ -6,6 +6,18 @@ straightforward as is documented near the end of
However, deploying is not always as straightforward as the process
described there.
+<!-- TODO: make this fit in here:
+Speaking of the local repository, all the dependencies you pull in
+using Leiningen or Maven get cached in `$HOME/.m2/repository` since
+Leiningen uses the same library as Maven under the covers. You can
+install the current project in the local repository with this command:
+ $ lein install
+ Wrote ~/src/my-stuff/target/pom.xml
+ [INFO] Installing my-stuff-0.1.0-SNAPSHOT.jar to ~/.m2/repository/myproject/myproject/0.1.0-SNAPSHOT/myproject-0.1.0-SNAPSHOT.jar
## Clojars Forks
Sometimes you'll need to publish libraries that you don't directly
@@ -33,7 +45,7 @@ to Clojars.
There may be times when you want to make a library available to your
team without making it public. This is best done by setting up a
-private Maven repository. Both [Archiva](
+private repository. Both [Archiva](
and [Nexus]( will allow you to set up
private, password-protected repositories. These also provide proxying
to other repositories, so you can set `:omit-default-repositories`
Oops, something went wrong.

0 comments on commit cd9a496

Please sign in to comment.