I always found the maven release plugin to be a pain to work with in
practice. Switching to an alternative like git makes most of that stuff
unnecessary. You just need a simple "git tag" command to tag the release
and with gradle you only really have to set the version in one place,
rather than in every single pom of a multiproject build. With git you
can get everything in place before pushing it out in the state you want,
rather than having to mess about with remote operations and svn
branching/tagging.
With the setup we have now, I don't really see much need for the
functionality the maven release plugin offers. Of course it could be
possible to add value to release management in other ways :).
On 03/08/2010 06:02, Adam Murdoch wrote:
On 29/07/10 6:47 PM, [email protected] wrote:
Hi all,
I just started with Gradle and try to migrate some maven projects to
gradle.
I found in the roadmap that "Release management" is Post 1.0 - which I
assume is similar to the maven release plugin, right ?
Similar in intention, yes. Probably not similar in implementation.
Does this mean that currently to make a release one has to do the
different steps (make sure everything is correct, SCM tagging, version
number increase etc) manually ?
Yes.
Of course, if someone wants to pop that stuff in a plugin and share it
with others, that would be most appreciated, and a good start towards
some release management support in Gradle. Before 1.0 is finished, we
want to make it much easier to author and share plugins like this with
others.
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
CTO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
