We're using gitflow/maven quite nicely, I use for my release plugin:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.1</version>
<configuration>
<goals>deploy</goals>
<pushChanges>false</pushChanges>
<localCheckout>true</localCheckout>
</configuration>
</plugin>
In this configuration maven does a local checkout, and doesn't require a git
push during release. This means after a maven release, I do my git-flow
release, THEN push the master/develop branch to my origin.
In my default setup, if I want to push the tags I still have to run "git push
--tags", but I also get the opportunity to remove any tags I don't want to push.
On 26/07/2011, at 1:31 AM, Lars Fischer wrote:
> Hello,
>
> I use git together with gitflow(1) and would like to release projects the
> gitflow way. Gitflow itself creates branches, a release tag and merges
> changes back into other branches.
>
> The maven-release-plugin performs similar things an other way. I tried to
> use both together, but it works only with hacks and results in confusing or
> not correct tags.
>
> Is there a kind of "lightweight" release-plugin, which does only perform
> - version-checks and updates (remove SNAPSHOTs)
> - build and test the changed project
> - commit the changes into the current branch if everything is correct
>
> It should NOT create a tag or push changes.
>
>
> [1] http://nvie.com/posts/a-successful-git-branching-model/
> http://yakiloo.com/getting-started-git-flow/
>
>
> Regards,
> Lars
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
