Bump version to 1.4.0-SNAPSHOT.

This commit is contained in:
Phil Hagelberg 2010-08-20 13:58:50 -07:00
parent 6dbfd8b2a9
commit 5b76514ea6
5 changed files with 15 additions and 17 deletions

View file

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

View file

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

View file

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

View file

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

View file

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