You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jan Novotný (JIRA)" <ji...@codehaus.org> on 2014/01/24 10:30:49 UTC

[jira] (MRELEASE-864) Maven Release Plugin releases SNAPSHOT instead of STABLE version

Jan Novotný created MRELEASE-864:
------------------------------------

             Summary: Maven Release Plugin releases SNAPSHOT instead of STABLE version
                 Key: MRELEASE-864
                 URL: https://jira.codehaus.org/browse/MRELEASE-864
             Project: Maven Release Plugin
          Issue Type: Bug
          Components: Git
         Environment: Everywhere with maven-scm-provider-gitexe of version 1.9 (and maybe older)
            Reporter: Jan Novotný
         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 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira