Yeah, I know it's not possible for everyone to switch their source
control system, but it's also a tall order for something like gradle to
support them all out of the box. My practical experience with trying to
use things like maven's SCM support and bugs in the release-plugin
invariably led me to use the command-line tools for tagging a release,
even when we were using svn. To my mind, most of the rest of the
functionality of the maven release plugin is either unnecessary with
gradle, or can be achieved easily by declaring tasks.
On 03/08/2010 13:29, [email protected] wrote:
I know that the release plugin is kind of hell, but your assumption that
"just use git" is unfortunately not valid everywhere. As there are
several SCM systems available it would be wrong to state "because with
git everything is working, so no need for that".
And I didnt ask for the exact same behaviour of the maven release
plugin. If something which tags the sources and updates the versions and
uploads the artifacts somehow is working I think thats more than enough
- as Adam sayed "Similar in intention, yes. Probably not similar in
implementation."
-----Original Message-----
From: Luke Taylor <[email protected]>
To: user <[email protected]>
Sent: Tue, Aug 3, 2010 2:13 pm
Subject: Re: [gradle-user] Making a Release in Gradle
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] <mailto:[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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
