Martijn, just a guess:
- there is a setting in release:prepare for remote tagging which must be
false as well if I remember correctly.
Regards
Mirko
--
Sent from my mobile
On Dec 26, 2013 4:49 PM, "Martijn Dashorst" <martijn.dasho...@gmail.com>
wrote:
> Is it me or does the maven-release-plugin ignore the pushChanges setting?
>
> Running the release process actually pushes the changes to the git
> repo. And I *really* don't want that to happen.
>
> Relevant configuration:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.4.2</version>
> <inherited>true</inherited>
> <configuration>
> <pushChanges>false</pushChanges>
> <tagNameFormat>wicket-@{project.version}</tagNameFormat>
> <updateWorkingCopyVersions>false</updateWorkingCopyVersions>
> </configuration>
> </plugin>
>
>
> $ git --version
> git version 1.8.5.2
>
> $ mvn --version
> Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a;
> 2013-09-17 17:22:22+0200)
> Maven home: /usr/local/Cellar/maven/3.1.1/libexec
> Java version: 1.7.0_45, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.9.1", arch: "x86_64", family: "mac"
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
