Mostly todos.

README.md

@@ -85,7 +85,7 @@ advantage of this, you should put it on your <tt>$PATH</tt>.
 Place a <tt>project.clj</tt> file in the project root like this:
 
     (defproject leiningen "0.5.0-SNAPSHOT"
-      :description "A build tool designed not to set your hair on fire."
+      :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"]

bin/lein

@@ -38,7 +38,7 @@ LEIN_PLUGINS="$(ls -1 lib/dev/*jar 2> /dev/null | tr \\n \:)"
 LEIN_USER_PLUGINS="$(ls -1 $LEIN_HOME/plugins/*jar 2> /dev/null | tr \\n \:)"
 CLASSPATH=$LEIN_USER_PLUGINS:$LEIN_PLUGINS:src/:$CLASSPATH
 LEIN_JAR="$HOME/.m2/repository/leiningen/leiningen/$LEIN_VERSION/leiningen-$LEIN_VERSION-standalone.jar"
-CLOJURE_JAR="$HOME/.m2/repository/org/clojure/clojure/1.2.0/clojure-1.2.0.jar"
+# CLOJURE_JAR="$HOME/.m2/repository/org/clojure/clojure/1.2.0/clojure-1.2.0.jar"
 NULL_DEVICE=/dev/null
 
 # normalize $0 on certain BSDs

src/leiningen/core.clj

@@ -10,7 +10,7 @@
 (defn- unquote-project [args]
   (walk (fn [item]
           (cond (and (seq? item) (= `unquote (first item))) (second item)
-                ;; needed if we want fn literals to be usable by eval-in-project:
+                ;; needed if we want fn literals to be usable by eval-in-project
                 (and (seq? item) (= 'fn (first item))) (list 'quote item)
                 (symbol? item) (list 'quote item)
                 :else (unquote-project item)))

todo.org

@@ -19,10 +19,13 @@ See also http://github.com/technomancy/leiningen/issues
    just use Maven's notion of the project's dependencies to construct a
    classpath that references jars straight from ~/.m2.
 * For 1.4
+** TODO merge push task based on clj-ssh
 ** TODO plugin task for managing/upgrading plugins
    Manually copying jar files into ~/.lein/plugins is pretty
    lame. Let's get a task to handle this. It could be implemented as a
    plugin at first, maybe.
+** TODO integrate plugin task with lein-search
+   Would be better to be able to leave off version numbers
 ** TODO merge lein-search features?
    This plugin is great; we should think about taking it into
    Leiningen itself.
@@ -42,6 +45,7 @@ See also http://github.com/technomancy/leiningen/issues
 ** TODO spin lancet off into its own dependency
    I've never felt comfortable about simply keeping it inline. On the
    other hand if we quit using ant then we can skip this.
+   Needs to not be in the default package!
 ** TODO shell wrappers should support multiple versions
    We could write out a different "foo-$VERSION" shell wrapper for each
    version of a project that gets installed and then have the plain
@@ -49,6 +53,7 @@ See also http://github.com/technomancy/leiningen/issues
    just fall back to the latest.
 ** TODO fail gracefully when run without an Internet connection (Issue #100)
 ** TODO improve test coverage
+** TODO expose original cwd as property
 ** DONE test selectors using metadata; run a subset of tests
    We could have a :test-selectors key in project.clj that would map
    keywords to predicate functions. Then the test task could take a