The maven release plugin does pretty much that, only it doesn't do any ivy stuff. However, it also checks:
* No uncommitted files * No files in working copy that are not under VCS * Automatically tags (and optionally branches) the code at time of release * Automatically incremements your version numbers Its very handy. -- Pull me down under... On Thu, Oct 15, 2009 at 7:30 PM, Meikel Brandmeyer <m...@kotka.de> wrote: > I don't really know what the maven release plugin does. And since I'm > not a professional software developer I also don't really know what > it's supposed to do. With gradle you define a task (uploadArchives) > which specifies repositories, where the resulting artifacts are > supposed to be published. For maven repos it generates a pom.xml, for > Ivy it generates an ivy.xml and for a simple ftp site it just puts the > file there. At least this is my understanding how it works. For me > this is sufficient. One can also have multiple archive definitions > containing differents sets of artifacts with different upload tasks. > So there is also some flexibility if necessary. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
