[
https://jira.codehaus.org/browse/SCM-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340818#comment-340818
]
Romain Deltour commented on SCM-740:
------------------------------------
I've been hit with the very same issue. I confirm that the build available at
the referenced blog post fixed it for me (many thanks Jan!).
My config:
{noformat}
maven-release-plugin:2.4.2 / maven-scm-provider-gitexe:1.9
$ git --version
git version 1.8.5.3
$ 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"
{noformat}
> Maven Release Plugin releases SNAPSHOT instead of STABLE version
> ----------------------------------------------------------------
>
> Key: SCM-740
> URL: https://jira.codehaus.org/browse/SCM-740
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Environment: Everywhere with maven-scm-provider-gitexe of version 1.9
> (and maybe older)
> Reporter: Jan Novotný
> Attachments: Wrong_base_directory_used1.patch
>
>
> If you have following project structure:
> - superproject [Git repository root]
> - projectA [release target]
> - projectB [release target]
> in other words you release subproject of a larger Git repository separately,
> you probably run at the same issue as we did. No recipe from above mentioned
> sources solves your problems and during release:prepare phase still no commit
> of stable pom.xml occurs. There is another bug in GitStatusConsumer class
> that checks output of the git status --porcelain command and verifies
> existency of the mentioned files on local filesystem. Regretfully it uses
> working directory instead of git repository root as the base folder and thus
> it constructs invalid path to the file where project folder directory is
> duplicated.
> Problem is better described here:
> http://blog.novoj.net/2014/01/24/maven-release-plugin-releases-snapshot-instead-of-stable-version
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
