[
https://jira.codehaus.org/browse/MRELEASE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351340#comment-351340
]
Koen Serneels edited comment on MRELEASE-812 at 8/12/14 3:10 PM:
-----------------------------------------------------------------
I was experiencing the same issue (Git 1.9.1/Ubuntu). The release plugin (was
using 2.4.2) would not commit anymore, resulting in the SNAPSHOT suffix being
present in the tag.
Bumping the release plugin to 2.5 solved the problem for projects having the
pom.xml in the repository root.
However, I had another project with the pom.xml NOT directly in the repository
root. For this bumping to 2.5 alone was not enough. To fix this the SCM api
and gitexe dependency also need to be overridden to the latest version (1.9.1
atm). This solved the problem there as well with the release plugin still at
v2.5
{code}
<dependencies>
<dependency>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-api</artifactId>
<version>1.9.1</version>
</dependency>
<dependency>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-provider-gitexe</artifactId>
<version>1.9.1</version>
</dependency>
</dependencies>
{code}
See also https://jira.codehaus.org/browse/SCM-740
was (Author: koen.serneels):
I was experiencing the same issue (Git 1.9.1/Ubuntu). The release plugin (still
using 2.4.2) would not commit, resulting in the SNAPSHOT suffix being present
in the tag.
Bumping the release plugin to 2.5 solved the problem for projects having the
pom.xml in the repository root.
However, I had another project with the pom.xml NOT directly in the repository
root. For this overriding the SCM api and gitexe dependency to the latest
version (1.9.1 atm) solved the problem there as well (while still using the
latest release plugin version being 2.5 atm)
{code}
<dependencies>
<dependency>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-api</artifactId>
<version>1.9.1</version>
</dependency>
<dependency>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-provider-gitexe</artifactId>
<version>1.9.1</version>
</dependency>
</dependencies>
{code}
See also https://jira.codehaus.org/browse/SCM-740
> "prepare" does not commit before tagging and therefore deploys snapshot
> instead of release
> ------------------------------------------------------------------------------------------
>
> Key: MRELEASE-812
> URL: https://jira.codehaus.org/browse/MRELEASE-812
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: Git
> Affects Versions: 2.3.2, 2.4
> Reporter: Andrei Pozolotin
> Assignee: Robert Scholte
> Priority: Critical
> Fix For: 2.5
>
> Attachments: mvn-2.3.2.txt, mvn-2.4.0.txt
>
>
> thank you very much for new release!
> http://mail-archives.apache.org/mod_mbox/maven-announce/201212.mbox/%3Cop.wpjbptp1kdkhrr@columbia%3E
> it seems we need an emergency fix:
> attached are 2 logs:
> 1) mvn-2.3.2.txt invocation that works fine with 2.3.2
> 2) mvn-2.4.0.txt invocation that fails with 2.4
> problem:
> "perform" does not commit tags, deploys snapshot instead of release
> here is project parent:
> http://search.maven.org/remotecontent?filepath=com/barchart/base/barchart-archon/2.3.6/barchart-archon-2.3.6.pom
> build is invoked both times with this:
> mvn --define resume=false release:prepare
> mvn --define resume=false release:perform
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
