Uploaded image for project: 'Maven SCM'
  1. Maven SCM
  2. SCM-740

Maven Release Plugin releases SNAPSHOT instead of STABLE version

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.9.1
    • None
    • Everywhere with maven-scm-provider-gitexe of version 1.9 (and maybe older)
    • Patch

    Description

      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

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            struberg Mark Struberg
            novoj Jan Novotný
            Votes:
            6 Vote for this issue
            Watchers:
            19 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment