Bump version to 1.0.0-SNAPSHOT

README.md

@@ -26,7 +26,9 @@ rather than copying and pasting among each of your projects.
 
 ## Installation
 
-Copy bin/lein to a location on your $PATH and run: $ lein self-install
+1. Download the script: http://github.com/technomancy/leiningen/raw/master/bin/lein
+2. Place it on your path and chmod it to be executable.
+3. Run: <tt>lein self-install</tt>
 
 ## Usage
 
@@ -50,8 +52,6 @@ Copy bin/lein to a location on your $PATH and run: $ lein self-install
 
     $ lein help [TASK] # show a list of tasks or help for a given TASK
 
-TODO: new, deploy
-
 ## Configuration
 
 Place a project.clj file in the project root that looks something like this: 
@@ -111,12 +111,20 @@ necessary:
 
 0. Place bin/lein on your $PATH somewhere.
 1. Do a self-install of leiningen (from outside the checkout tree).
-2. Place ~/.leiningen.jar in lib.
+2. Place ~/.m2/repository/leiningen/leiningen/$VERSION/leiningen-$VERSION.jar in lib.
 3. Invoke "lein compile" followed by "lein deps".
 4. Remove .leiningen.jar from lib.
 5. Invoke "lein uberjar", and place the jar in ~/.leiningen.jar for
    future use.
 
+The [mailing list](http://groups.google.com/group/clojure) and the
+#leiningen or #clojure channels on Freenode are the best places to
+bring up questions or suggestions. Contributions are preferred as
+either Github pull requests or using "git format-patch" as described
+at http://clojure.org/patches.
+
+Please use standard indentation with no tabs or trailing whitespace.
+
 Leiningen is extensible, you can define new tasks in plugins. Add your
 plugin as a dev-dependency of your project, and you'll be able to call
 "lein $YOUR_COMMAND". See the lein-swank directory for an example of a

bin/lein

@@ -1,7 +1,7 @@
 #!/bin/bash
 
 # TODO: this gives us a trailing colon
-VERSION=0.5.0
+VERSION="1.0.0-SNAPSHOT"
 LIBS="$(find -H lib/ -mindepth 2> /dev/null 1 -maxdepth 1 -print0 | tr \\0 \:)"
 CLASSPATH="src/:classes/:$LIBS"
 LEIN_JAR=$HOME/.m2/repository/leiningen/leiningen/$VERSION/leiningen-$VERSION.jar

project.clj

@@ -2,7 +2,7 @@
 ;; defproject form. It can have other code in it as well, including
 ;; loading other task definitions.
 
-(defproject leiningen "0.5.0"
+(defproject leiningen "1.0.0-SNAPSHOT"
   :description "A build tool designed not to set your hair on fire."
   :main leiningen.core
   :dependencies [[org.clojure/clojure "1.1.0-alpha-SNAPSHOT"]
@@ -11,4 +11,5 @@
                  [org.apache.maven/maven-ant-tasks "2.0.10"]]
   ;; Wait till this makes it to a public repo.
   ;; :dev-dependencies [[org.clojure/swank-clojure "1.0"]]
+  :dev-dependencies [[lein-clojars "0.5.0-SNAPSHOT"]]
   )

src/leiningen/compile.clj

@@ -13,4 +13,5 @@ unless a list of :namespaces is provided in project.clj."
                 (find-namespaces-in-dir (file (:root project) "src")))]
     (println "Compiling" n)
     ;; TODO: check to see if bytecode is older than source
+    (require n)
     (clojure.core/compile n)))

src/leiningen/jar.clj

@@ -15,10 +15,11 @@
 the source .clj files. If project.clj contains a :main symbol, it will be used
 as the main-class for an executable jar."
   [project & args]
+  ;; TODO: clean?
   (compile/compile project)
   (let [jar-file (str (:root project) "/" (:name project) ".jar")
         filesets [{:dir *compile-path*}
-                  {:dir (str (:root project) "/src")}
+                  {:dir (str (:root project) "/src")} ; TODO: pom too
                   {:file (str (:root project) "/project.clj")}]]
     ;; TODO: support slim, etc
     (apply lancet/jar {:jarfile jar-file

src/leiningen/pom.clj

@@ -47,6 +47,9 @@
     (.setProject lancet/ant-project)
     (.setMavenProject (MavenProject. (make-model project)))))
 
+;; TODO: generated poms should use a different filename so we don't
+;; have to worry about overwriting existing ones?
+
 (defn pom [project & [args]]
   (let [pom-file (file (:root project) "pom.xml")]
     (with-open [w (writer pom-file)]