I have been using lein-release (https://github.com/relaynetwork/lein-release) for a while. It's surely nice to see this feature built into core.

On Tue 10 Jun 2014 06:11:06 PM CST, Atamert Ölçgen wrote:
Thanks for bringing deploy-repositories to my attention, I didn't know
it was there.



On Tue, Jun 10, 2014 at 5:22 AM, Phil Hagelberg <p...@hagelb.org
<mailto:p...@hagelb.org>> wrote:


    Greetings!

    I'm pleased to announce the release of Leiningen 2.4.0, our most
    significant release in quite some time. The star of the show is
    the new
    `release` task, which can automate all the common steps behind the
    release of a new version of a library.

    The idea is that `lein release` will run a series of tasks you've
    specified as release steps. This defaults to running the equivalent of
    these commands:

    * lein vcs assert-committed
    * lein change version leiningen.release/bump-version release
    * lein vcs commit
    * lein vcs tag
    * lein deploy
    * lein change version leiningen.release/bump-version patch
    * lein vcs commit
    * lein vcs push

    The `vcs` and `change` tasks are also new. The `vcs` subtasks
    above are
    self-explanatory, but the `change` task allows for programmatic
    modification of any given key in defproject using an arbitrary
    function,
    without altering formatting or comments. Out of the box we ship a
    function to bump version numbers, but you can call functions from
    plugins, and we hope to add more built-in functions in future
    releases.

    Note that the release task runs `lein deploy` rather than `lein deploy
    clojars`; this is in order to prevent accidental deploys of private
    artifacts to Clojars. In order to deploy an open source library to
    Clojars it's necessary to add `:deploy-repositories {"releases"
    :clojars}`
    to your project.clj file.

    Other highlights include fixes to the search task to report index
    download progress, improved multi-field queries, and the default
    to make
    useful uberjars even when not AOTing a -main function.

    A full list of significant changes:

    * Allow aliases to splice in values from the project map. (Phil
    Hagelberg)
    * Allow plugins to override built-in tasks. (Phil Hagelberg)
    * Add `release` task for automating common release steps. (Wayne
    Warren, Chris Truter, Phil Hagelberg)
    * Add `change` task for programmatc `project.clj` manipulation.
    (Chris Truter, Max Barnash)
    * Abort when `defproject` contains duplicate keys. (Peter Garbers)
    * Add `vcs` task to automate version control. (Phil Hagelberg,
    Wayne Warren)
    * Automatically `clean` before `deploy` to avoid AOT in libraries.
    (Phil Hagelberg)
    * Emit warnings to stderr. (Andy Chambers)
    * Use `clojure.main` for uberjars that don't declare their own
    `:main`. (Phil Hagelberg)
    * Allow templates to load from `:plugin-repositories`. (Phil
    Hagelberg)
    * Fix a race condition on printing during dependency resolution.
    (Phil Hagelberg)
    * Allow `new` templates to operate on existing directories with
    `--force` option. (Matthew Blair)
    * Fix `search` task to allow queries on multiple fields. (Colin Jones)
    * Fix a bug where errors in `run` task were mis-reported. (Gary
    Fredericks)
    * Report download progress of search indices. (Matthew Blair)
    * Protection from harmful `:clean-targets` settings. (Craig McDaniel)
    * Faster loading of help text. (David Grayson, Ryan Mulligan)
    * Add `LEIN_SILENT` option to suppress `*info*` output. (Phil
    Hagelberg)

    As usual, for those who manually installed `lein upgrade` will pull in
    the latest, and `lein upgrade 2.3.4` will back it down to the previous
    version if you run into any issues.

    Thanks to all the contributors who made this happen!

    -Phil

    ps. The Clojars artifacts for this release are still pending
    investigation of some deploy issues, but they should be right
    around the
    corner.






--
Kind Regards,
Atamert Ölçgen

-+-
--+
+++

www.muhuk.com <http://www.muhuk.com>

--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient
with your first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to clojure+unsubscr...@googlegroups.com
<mailto:clojure+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to