Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Fri, 24 Jan 2014 10:53:49 -0600 (CST)
From: "Robert Scholte (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Message-ID: 
 <JIRA.151511.1390555741569.4394.1390582429895@codehaus01.managed.contegix.com>
In-Reply-To: <JIRA.151511.1390555741569@codehaus01.managed.contegix.com>
References: <JIRA.151511.1390555741569@codehaus01.managed.contegix.com>
Subject: [jira] (SCM-740) Maven Release Plugin releases SNAPSHOT instead of
 STABLE version
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


    [ https://jira.codehaus.org/browse/SCM-740?page=3Dcom.atlassian.jira.pl=
ugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D339998#comme=
nt-339998 ]=20

Robert Scholte commented on SCM-740:
------------------------------------

Would be nice if this could be confirmed with a unittest.
               =20
> 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=FD
>         Attachments: Wrong_base_directory_used.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 separate=
ly, you probably run at the same issue as we did. No recipe from above ment=
ioned sources solves your problems and during release:prepare phase still n=
o commit of stable pom.xml occurs. There is another bug in GitStatusConsume=
r class that checks output of the git status --porcelain command and verifi=
es existency of the mentioned files on local filesystem. Regretfully it use=
s working directory instead of git repository root as the base folder and t=
hus it constructs invalid path to the file where project folder directory i=
s duplicated.
> Problem is better described here: http://blog.novoj.net/2014/01/24/maven-=
release-plugin-releases-snapshot-instead-of-stable-version

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira