maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herve Boutemy (JIRA)" <>
Subject [jira] (SCM-740) Maven Release Plugin releases SNAPSHOT instead of STABLE version
Date Sun, 11 May 2014 17:04:10 GMT


Herve Boutemy commented on SCM-740:

for the record, here is the commit [b4aee509|]

> Maven Release Plugin releases SNAPSHOT instead of STABLE version
> ----------------------------------------------------------------
>                 Key: SCM-740
>                 URL:
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-git
>         Environment: Everywhere with maven-scm-provider-gitexe of version 1.9 (and maybe
>            Reporter: Jan Novotný
>            Assignee: Mark Struberg
>             Fix For: 1.10
>         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:

This message was sent by Atlassian JIRA

View raw message