Bump version to 1.4.0-SNAPSHOT.

HACKING.md

@@ -45,9 +45,9 @@ TODO: integrate with plugin guide
 # Release Checklist
 
 * update NEWS, bin/lein, project.clj, pom
-* generate uberjar, upload
-* git tag
+* rm -rf lib, generate uberjar, upload
 * test self-install
+* git tag
 * push, push tags, update stable branch
 * announce on mailing list
 * bump version numbers (bin/lein and project.clj)

bin/lein

@@ -1,6 +1,6 @@
 #!/bin/sh
 
-VERSION="1.3.0"
+VERSION="1.4.0-SNAPSHOT"
 
 case $VERSION in
     *SNAPSHOT) SNAPSHOT="YES" ;;

pom.xml

@@ -3,7 +3,7 @@
   <modelVersion>4.0.0</modelVersion>
   <groupId>leiningen</groupId>
   <artifactId>leiningen</artifactId>
-  <version>1.3.0</version>
+  <version>1.4.0-SNAPSHOT</version>
   <name>leiningen</name>
   <description>A build tool designed not to set your hair on fire.</description>
   <url>http://github.com/technomancy/leiningen</url>
@@ -15,7 +15,7 @@
   <scm>
     <connection>scm:git:git://github.com/technomancy/leiningen.git</connection>
     <developerConnection>scm:git:ssh://git@github.com/technomancy/leiningen.git</developerConnection>
-    <tag>7efb72f9635239b4853d22265b95239bc3c18fe7</tag>
+    <tag>6dbfd8b2a9fcd870045c2bc755ef38f56b9f9bb6</tag>
     <url>http://github.com/technomancy/leiningen</url>
   </scm>
   <build>

project.clj

@@ -2,7 +2,7 @@
 ;; defproject form. It can have other code in it as well, including
 ;; loading other task definitions.
 
-(defproject leiningen "1.3.0"
+(defproject leiningen "1.4.0-SNAPSHOT"
   :description "A build tool designed not to set your hair on fire."
   :url "http://github.com/technomancy/leiningen"
   :license {:name "Eclipse Public License"}

todo.org

@@ -8,8 +8,8 @@ Leiningen TODOs
 * For 1.4.0 or later
 ** TODO add option to use ~/.m2-based classpath instead of copying to lib/?
 ** TODO plugin task for managing/upgrading plugins
-** TODO lein add $DEPENDENCY (inserts it into :dependencies in project.clj)
 ** TODO shell wrappers should support multiple versions
+** TODO merge lein-search features?
 ** TODO classifiers for specifying what clojure version to use?
 ** TODO test classification using metadata; run a subset of tests
 ** TODO a list of dirs to include in the jar when building
@@ -67,13 +67,11 @@ Leiningen TODOs
 ** DONE Allow test task to take namespaces as an argument
 ** DONE Fix eval-in-project to let plugins pass in extra args
 ** DONE Resources directory added to classpath (for properties, etc)
-* Plugin Ideas:
-*** Code statistics (LOC, doc coverage, etc)
-*** Graph output for dependencies between namespaces
-*** Checkout task: install the jar in ~/.m2 and look for SCM repository metadata
-*** Start web server for web-related projects
-*** Multi-module builds
-*** Repository search
-* Low Priority
-** TODO Run failed tests task
-** TODO Remove duplication between deps.clj and pom.clj
+* Git-aware dependencies (experimental back-burner idea)
+  Talking with Rich after Emerging Langs day 1
+  Problem: you can pull in two versions of the same library
+  transitively without realizing it if people fork on clojars. How do
+  we detect this problem and de-dupe?
+** What if artifacts could be correlated with the git rev that produced them?
+** They have repository and sha1 metadata in their pom (but no history tree)
+** Cross-correlate with a separate revision metadata store?