[
https://jira.codehaus.org/browse/MRELEASE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341842#comment-341842
]
John Casey edited comment on MRELEASE-812 at 2/21/14 12:19 PM:
---------------------------------------------------------------
I've seen this happening in version 2.3.2 also.
I'm just adding this to help others searching for solutions to this. It's a
VERY difficult problem to understand until you sift through the debug console
output...and even then, you have to know what to look for.
If you're using Maven 3.1.1, this behavior will crop up if you don't have a
version specified for the release plugin in your pom.xml, since it seems to be
the default version.
>From an execution using Maven 3.1.1 and release 2.3.2:
{noformat}
[DEBUG] On branch master
[DEBUG] Your branch is up-to-date with 'origin/master'.
[DEBUG]
[DEBUG] Changes to be committed:
[DEBUG] (use "git reset HEAD <file>..." to unstage)
[DEBUG]
[DEBUG] modified: pom.xml
[DEBUG]
[DEBUG] Untracked files:
[DEBUG] (use "git add <file>..." to include in what will be committed)
[DEBUG]
[DEBUG] pom.xml.releaseBackup
[DEBUG] prepare.log
[DEBUG] release.properties
[DEBUG]
[INFO] Tagging release with the label buildmetadata-maven-plugin-1.3.1...
{noformat}
was (Author: jdcasey):
I've seen this happening in version 2.3.2 also.
I'm just adding this to help others searching for solutions to this. It's a
VERY difficult problem to understand until you sift through the debug console
output...and even then, you have to know what to look for.
If you're using Maven 3.1.1, this behavior will crop up if you don't have a
version specified for the release plugin in your pom.xml, since it seems to be
the default version.
> "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)
