In my own git based projects:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.3.1</version>
<configuration>
<!--<preparationGoals>clean verify
youtrack:update-version youtrack:merge-changes
changes:announcement-mail</preparationGoals>-->
<preparationGoals>clean install</preparationGoals>
<autoVersionSubmodules>true</autoVersionSubmodules>
<goals>deploy</goals>
<pushChanges>false</pushChanges>
<localCheckout>true</localCheckout>
</configuration>
</plugin>
Here I configured that the release plugin should NOT push changes during
release ( I don't want my release branches escaping to the remote
repository ), and to use local checkout/clone from the local repository.
There -was- a bug in the last release plugin that under certain crashes
it wasn't cleaning up release.properties properly which has since been
fixed.
One main issue to be aware of with git ( and I assume mercurial ) is
that you HAVE to release from the root of your repository, which pushes
you to a single module/artifact per repository.
On 21/06/12 9:11 AM, Ricky Clarkson wrote:
How do you have your release plugin/scm plugin configured, Fabrizio,
for that to work from git? I saw that various things had changed to
make that possible due to a number of complaints but haven't tried
them out.
--
You received this message because you are subscribed to the Google Groups "Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
