Maven Release Plugin
  1. Maven Release Plugin
  2. MRELEASE-875

release:prepare does not commit pom.xml if not in the git root

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.5
    • Fix Version/s: 2.5.1
    • Component/s: prepare, scm
    • Labels:
      None
    • Environment:
      git 1.9.0

      Description

      When the project pom.xml is not in the Git project root (f.e. in the "src" directory) the pom.xml not committed and pushed (before tagging)
      Commit of the pom.xml during release:prepare works fine if it is in the / (root) of the git repository
      Using the pom.xml in a subdirectory worked well with version 2.4.2 using git 1.7.

        Issue Links

          Activity

          Hide
          Robert Scholte added a comment -

          Version 2.5 was a Git special release, which should have fixed this issue (SCM-709). A couple of users confirmed that this fixed their issues, so I'm surprised you hit it again.
          To narrow the issue: how about the combinations m-release-p-2.4.2 + Git 1.9.0 and m-release-p-2.5 + Git 1.7?
          When running with debug logging (add -X or --debug to your commandline), you'll see the Git commandlines being executed. What do you see and what should it be?

          Show
          Robert Scholte added a comment - Version 2.5 was a Git special release, which should have fixed this issue ( SCM-709 ). A couple of users confirmed that this fixed their issues, so I'm surprised you hit it again. To narrow the issue: how about the combinations m-release-p-2.4.2 + Git 1.9.0 and m-release-p-2.5 + Git 1.7? When running with debug logging (add -X or --debug to your commandline), you'll see the Git commandlines being executed. What do you see and what should it be?
          Hide
          john ten Den added a comment - - edited

          First the requested debug logging m-release-p-2.5 + Git 1.9.0

          1) pom.xml not in Git root (but in directory indirectory)
          marked

          {>>> comment where i expected other behaviour}

          =============================================

          INFO] Checking in modified POMs...
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git add – pom.xml
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git rev-parse --show-toplevel
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git status --porcelain .
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [DEBUG] M indirectory/pom.xml
          [DEBUG] ?? indirectory/pom.xml.releaseBackup
          [WARNING] Ignoring unrecognized line: ?? indirectory/pom.xml.releaseBackup
          [DEBUG] ?? indirectory/release.properties
          [WARNING] Ignoring unrecognized line: ?? indirectory/release.properties

          {>>> Expected commit and push of the modified indirectory/pom.xml}
          [INFO] Tagging release with the label johntest2-0.0.2...
          [DEBUG] ScmTagPhase :: scmTagParameters remotingTag true
          [DEBUG] ScmTagPhase :: scmTagParameters scmRevision null
          [DEBUG] ScmTagPhase :: fileSet basedir = /Users/johntenden/projecten/git/bier/indirectory; files = []
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git tag -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw9000000gn/T/maven-scm-24639574.commit johntest2-0.0.2
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git push git@git.trivento.nl:john/bier.git refs/tags/johntest2-0.0.2
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git ls-files
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [DEBUG] pom.xml
          [INFO] Transforming 'johntest'...
          [INFO] Not removing release POMs
          [INFO] Checking in modified POMs...
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git add – pom.xml
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git rev-parse --show-toplevel
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git status --porcelain .
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [DEBUG] M indirectory/pom.xml
          [DEBUG] ?? indirectory/pom.xml.releaseBackup
          [WARNING] Ignoring unrecognized line: ?? indirectory/pom.xml.releaseBackup
          [DEBUG] ?? indirectory/release.properties
          [WARNING] Ignoring unrecognized line: ?? indirectory/release.properties
          {>>> Expected commit and push of the modified indirectory/pom.xml}

          [INFO] Release preparation complete.
          [INFO] ------------------------------------------------------------------------
          [INFO] BUILD SUCCESS
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 11.040 s
          [INFO] Finished at: 2014-04-11T09:16:43+01:00
          [INFO] Final Memory: 11M/222M
          [INFO] ------------------------------------------------------------------------

          2) pom.xml in Git root : Working fine !
          ==============================
          [INFO] [INFO] ------------------------------------------------------------------------
          [INFO] [INFO] BUILD SUCCESS
          [INFO] [INFO] ------------------------------------------------------------------------
          [INFO] [INFO] Total time: 0.540 s
          [INFO] [INFO] Finished at: 2014-04-11T09:24:09+01:00
          [INFO] [INFO] Final Memory: 5M/123M
          [INFO] [INFO] ------------------------------------------------------------------------
          [INFO] Checking in modified POMs...
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git add – pom.xml
          [INFO] Working directory: /Users/johntenden/projecten/git/bier
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git rev-parse --show-toplevel
          [INFO] Working directory: /Users/johntenden/projecten/git/bier
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git status --porcelain .
          [INFO] Working directory: /Users/johntenden/projecten/git/bier
          [DEBUG] M pom.xml
          [DEBUG] ?? pom.xml.releaseBackup
          [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup
          [DEBUG] ?? release.properties
          [WARNING] Ignoring unrecognized line: ?? release.properties
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git commit --verbose -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw9000000gn/T/maven-scm-1011576472.commit pom.xml
          [INFO] Working directory: /Users/johntenden/projecten/git/bier
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git symbolic-ref HEAD
          [INFO] Working directory: /Users/johntenden/projecten/git/bier
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git push git@git.trivento.nl:john/bier.git refs/heads/master:refs/heads/master
          [INFO] Working directory: /Users/johntenden/projecten/git/bier
          [INFO] Tagging release with the label johntest-0.0.2...
          [DEBUG] ScmTagPhase :: scmTagParameters remotingTag true
          [DEBUG] ScmTagPhase :: scmTagParameters scmRevision null
          [DEBUG] ScmTagPhase :: fileSet basedir = /Users/johntenden/projecten/git/bier; files = []
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git tag -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw9000000gn/T/maven-scm-1340971298.commit johntest-0.0.2
          [INFO] Working directory: /Users/johntenden/projecten/git/bier
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git push git@git.trivento.nl:john/bier.git refs/tags/johntest-0.0.2
          [INFO] Working directory: /Users/johntenden/projecten/git/bier
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git ls-files
          [INFO] Working directory: /Users/johntenden/projecten/git/bier
          [DEBUG] indirectory/pom.xml
          [DEBUG] pom.xml
          [INFO] Transforming 'johntest'...
          [INFO] Not removing release POMs
          [INFO] Checking in modified POMs...
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git add – pom.xml
          [INFO] Working directory: /Users/johntenden/projecten/git/bier
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git rev-parse --show-toplevel
          [INFO] Working directory: /Users/johntenden/projecten/git/bier
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git status --porcelain .
          [INFO] Working directory: /Users/johntenden/projecten/git/bier
          [DEBUG] M pom.xml
          [DEBUG] ?? pom.xml.releaseBackup
          [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup
          [DEBUG] ?? release.properties
          [WARNING] Ignoring unrecognized line: ?? release.properties
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git commit --verbose -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw9000000gn/T/maven-scm-364960822.commit pom.xml
          [INFO] Working directory: /Users/johntenden/projecten/git/bier
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git symbolic-ref HEAD
          [INFO] Working directory: /Users/johntenden/projecten/git/bier
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git push git@git.trivento.nl:john/bier.git refs/heads/master:refs/heads/master
          [INFO] Working directory: /Users/johntenden/projecten/git/bier
          [INFO] Release preparation complete.
          [INFO] ------------------------------------------------------------------------
          [INFO] BUILD SUCCESS
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 13.402 s
          [INFO] Finished at: 2014-04-11T09:24:13+01:00
          [INFO] Final Memory: 11M/222M
          [INFO] ------------------------------------------------------------------------

          Show
          john ten Den added a comment - - edited First the requested debug logging m-release-p-2.5 + Git 1.9.0 1) pom.xml not in Git root (but in directory indirectory) marked {>>> comment where i expected other behaviour} ============================================= INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git add – pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git rev-parse --show-toplevel [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git status --porcelain . [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [DEBUG] M indirectory/pom.xml [DEBUG] ?? indirectory/pom.xml.releaseBackup [WARNING] Ignoring unrecognized line: ?? indirectory/pom.xml.releaseBackup [DEBUG] ?? indirectory/release.properties [WARNING] Ignoring unrecognized line: ?? indirectory/release.properties {>>> Expected commit and push of the modified indirectory/pom.xml} [INFO] Tagging release with the label johntest2-0.0.2... [DEBUG] ScmTagPhase :: scmTagParameters remotingTag true [DEBUG] ScmTagPhase :: scmTagParameters scmRevision null [DEBUG] ScmTagPhase :: fileSet basedir = /Users/johntenden/projecten/git/bier/indirectory; files = [] [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git tag -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw9000000gn/T/maven-scm-24639574.commit johntest2-0.0.2 [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git push git@git.trivento.nl:john/bier.git refs/tags/johntest2-0.0.2 [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git ls-files [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [DEBUG] pom.xml [INFO] Transforming 'johntest'... [INFO] Not removing release POMs [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git add – pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git rev-parse --show-toplevel [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git status --porcelain . [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [DEBUG] M indirectory/pom.xml [DEBUG] ?? indirectory/pom.xml.releaseBackup [WARNING] Ignoring unrecognized line: ?? indirectory/pom.xml.releaseBackup [DEBUG] ?? indirectory/release.properties [WARNING] Ignoring unrecognized line: ?? indirectory/release.properties {>>> Expected commit and push of the modified indirectory/pom.xml} [INFO] Release preparation complete. [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 11.040 s [INFO] Finished at: 2014-04-11T09:16:43+01:00 [INFO] Final Memory: 11M/222M [INFO] ------------------------------------------------------------------------ 2) pom.xml in Git root : Working fine ! ============================== [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Total time: 0.540 s [INFO] [INFO] Finished at: 2014-04-11T09:24:09+01:00 [INFO] [INFO] Final Memory: 5M/123M [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git add – pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git rev-parse --show-toplevel [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git status --porcelain . [INFO] Working directory: /Users/johntenden/projecten/git/bier [DEBUG] M pom.xml [DEBUG] ?? pom.xml.releaseBackup [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup [DEBUG] ?? release.properties [WARNING] Ignoring unrecognized line: ?? release.properties [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git commit --verbose -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw9000000gn/T/maven-scm-1011576472.commit pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git symbolic-ref HEAD [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git push git@git.trivento.nl:john/bier.git refs/heads/master:refs/heads/master [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Tagging release with the label johntest-0.0.2... [DEBUG] ScmTagPhase :: scmTagParameters remotingTag true [DEBUG] ScmTagPhase :: scmTagParameters scmRevision null [DEBUG] ScmTagPhase :: fileSet basedir = /Users/johntenden/projecten/git/bier; files = [] [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git tag -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw9000000gn/T/maven-scm-1340971298.commit johntest-0.0.2 [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git push git@git.trivento.nl:john/bier.git refs/tags/johntest-0.0.2 [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git ls-files [INFO] Working directory: /Users/johntenden/projecten/git/bier [DEBUG] indirectory/pom.xml [DEBUG] pom.xml [INFO] Transforming 'johntest'... [INFO] Not removing release POMs [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git add – pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git rev-parse --show-toplevel [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git status --porcelain . [INFO] Working directory: /Users/johntenden/projecten/git/bier [DEBUG] M pom.xml [DEBUG] ?? pom.xml.releaseBackup [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup [DEBUG] ?? release.properties [WARNING] Ignoring unrecognized line: ?? release.properties [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git commit --verbose -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw9000000gn/T/maven-scm-364960822.commit pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git symbolic-ref HEAD [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier && git push git@git.trivento.nl:john/bier.git refs/heads/master:refs/heads/master [INFO] Working directory: /Users/johntenden/projecten/git/bier [INFO] Release preparation complete. [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 13.402 s [INFO] Finished at: 2014-04-11T09:24:13+01:00 [INFO] Final Memory: 11M/222M [INFO] ------------------------------------------------------------------------
          Hide
          john ten Den added a comment -

          I retested m-release-p2.4.2 with git 1.7.0 and its working well.
          Added trace of the indirectory/pom.xml below.
          I see that the git status 1.7.0 is returning the filelist relatieve to the path running from in this test case "indirectory")
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git status
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [DEBUG] # On branch master
          [DEBUG] # Your branch is ahead of 'origin/master' by 6 commits.
          [DEBUG] #
          [DEBUG] # Changes to be committed:
          [DEBUG] # (use "git reset HEAD <file>..." to unstage)
          [DEBUG] #
          [DEBUG] # modified: pom.xml
          [DEBUG] #
          [DEBUG] # Untracked files:
          [DEBUG] # (use "git add <file>..." to include in what will be committed)
          [DEBUG] #
          [DEBUG] # pom.xml.releaseBackup
          [DEBUG] # release.properties
          where the 1.9.0 is returning the filefiles relative to the git root:
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git status --porcelain .
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [DEBUG] M indirectory/pom.xml
          [DEBUG] ?? indirectory/pom.xml.releaseBackup
          [WARNING] Ignoring unrecognized line: ?? indirectory/pom.xml.releaseBackup
          [DEBUG] ?? indirectory/release.properties
          [WARNING] Ignoring unrecognized line: ?? indirectory/release.properties

          trace : m-release-p2.4.2 with git 1.7.0
          ==============================
          [INFO] [INFO] ------------------------------------------------------------------------
          [INFO] [INFO] BUILD SUCCESS
          [INFO] [INFO] ------------------------------------------------------------------------
          [INFO] [INFO] Total time: 0.534 s
          [INFO] [INFO] Finished at: 2014-04-11T09:42:37+01:00
          [INFO] [INFO] Final Memory: 6M/156M
          [INFO] [INFO] ------------------------------------------------------------------------
          [INFO] Checking in modified POMs...
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git add – pom.xml
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git status
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [DEBUG] # On branch master
          [DEBUG] # Your branch is ahead of 'origin/master' by 6 commits.
          [DEBUG] #
          [DEBUG] # Changes to be committed:
          [DEBUG] # (use "git reset HEAD <file>..." to unstage)
          [DEBUG] #
          [DEBUG] # modified: pom.xml
          [DEBUG] #
          [DEBUG] # Untracked files:
          [DEBUG] # (use "git add <file>..." to include in what will be committed)
          [DEBUG] #
          [DEBUG] # pom.xml.releaseBackup
          [DEBUG] # release.properties
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git commit --verbose -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw9000000gn/T/maven-scm-1159491710.commit pom.xml
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git symbolic-ref HEAD
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git push git@git.trivento.nl:john/bier.git master:master
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Tagging release with the label johntest2-0.0.3...
          [DEBUG] ScmTagPhase :: scmTagParameters remotingTag true
          [DEBUG] ScmTagPhase :: scmTagParameters scmRevision null
          [DEBUG] ScmTagPhase :: fileSet basedir = /Users/johntenden/projecten/git/bier/indirectory; files = []
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git tag -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw9000000gn/T/maven-scm-1210701058.commit johntest2-0.0.3
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git push git@git.trivento.nl:john/bier.git johntest2-0.0.3
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git ls-files
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [DEBUG] pom.xml
          [INFO] Transforming 'johntest'...
          [INFO] Not removing release POMs
          [INFO] Checking in modified POMs...
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git add – pom.xml
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git status
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [DEBUG] # On branch master
          [DEBUG] # Your branch is ahead of 'origin/master' by 7 commits.
          [DEBUG] #
          [DEBUG] # Changes to be committed:
          [DEBUG] # (use "git reset HEAD <file>..." to unstage)
          [DEBUG] #
          [DEBUG] # modified: pom.xml
          [DEBUG] #
          [DEBUG] # Untracked files:
          [DEBUG] # (use "git add <file>..." to include in what will be committed)
          [DEBUG] #
          [DEBUG] # pom.xml.releaseBackup
          [DEBUG] # release.properties
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git commit --verbose -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw9000000gn/T/maven-scm-927421259.commit pom.xml
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git symbolic-ref HEAD
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git push git@git.trivento.nl:john/bier.git master:master
          [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory
          [INFO] Release preparation complete.
          [INFO] ------------------------------------------------------------------------
          [INFO] BUILD SUCCESS
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 18.936 s
          [INFO] Finished at: 2014-04-11T09:42:49+01:00
          [INFO] Final Memory: 10M/156M

          Show
          john ten Den added a comment - I retested m-release-p2.4.2 with git 1.7.0 and its working well. Added trace of the indirectory/pom.xml below. I see that the git status 1.7.0 is returning the filelist relatieve to the path running from in this test case "indirectory") [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git status [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [DEBUG] # On branch master [DEBUG] # Your branch is ahead of 'origin/master' by 6 commits. [DEBUG] # [DEBUG] # Changes to be committed: [DEBUG] # (use "git reset HEAD <file>..." to unstage) [DEBUG] # [DEBUG] # modified: pom.xml [DEBUG] # [DEBUG] # Untracked files: [DEBUG] # (use "git add <file>..." to include in what will be committed) [DEBUG] # [DEBUG] # pom.xml.releaseBackup [DEBUG] # release.properties where the 1.9.0 is returning the filefiles relative to the git root: [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git status --porcelain . [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [DEBUG] M indirectory/pom.xml [DEBUG] ?? indirectory/pom.xml.releaseBackup [WARNING] Ignoring unrecognized line: ?? indirectory/pom.xml.releaseBackup [DEBUG] ?? indirectory/release.properties [WARNING] Ignoring unrecognized line: ?? indirectory/release.properties trace : m-release-p2.4.2 with git 1.7.0 ============================== [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Total time: 0.534 s [INFO] [INFO] Finished at: 2014-04-11T09:42:37+01:00 [INFO] [INFO] Final Memory: 6M/156M [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git add – pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git status [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [DEBUG] # On branch master [DEBUG] # Your branch is ahead of 'origin/master' by 6 commits. [DEBUG] # [DEBUG] # Changes to be committed: [DEBUG] # (use "git reset HEAD <file>..." to unstage) [DEBUG] # [DEBUG] # modified: pom.xml [DEBUG] # [DEBUG] # Untracked files: [DEBUG] # (use "git add <file>..." to include in what will be committed) [DEBUG] # [DEBUG] # pom.xml.releaseBackup [DEBUG] # release.properties [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git commit --verbose -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw9000000gn/T/maven-scm-1159491710.commit pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git symbolic-ref HEAD [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git push git@git.trivento.nl:john/bier.git master:master [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Tagging release with the label johntest2-0.0.3... [DEBUG] ScmTagPhase :: scmTagParameters remotingTag true [DEBUG] ScmTagPhase :: scmTagParameters scmRevision null [DEBUG] ScmTagPhase :: fileSet basedir = /Users/johntenden/projecten/git/bier/indirectory; files = [] [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git tag -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw9000000gn/T/maven-scm-1210701058.commit johntest2-0.0.3 [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git push git@git.trivento.nl:john/bier.git johntest2-0.0.3 [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git ls-files [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [DEBUG] pom.xml [INFO] Transforming 'johntest'... [INFO] Not removing release POMs [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git add – pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git status [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [DEBUG] # On branch master [DEBUG] # Your branch is ahead of 'origin/master' by 7 commits. [DEBUG] # [DEBUG] # Changes to be committed: [DEBUG] # (use "git reset HEAD <file>..." to unstage) [DEBUG] # [DEBUG] # modified: pom.xml [DEBUG] # [DEBUG] # Untracked files: [DEBUG] # (use "git add <file>..." to include in what will be committed) [DEBUG] # [DEBUG] # pom.xml.releaseBackup [DEBUG] # release.properties [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git commit --verbose -F /var/folders/s6/8zrhrmyj28d6smh9dm9sw9000000gn/T/maven-scm-927421259.commit pom.xml [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git symbolic-ref HEAD [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Executing: /bin/sh -c cd /Users/johntenden/projecten/git/bier/indirectory && git push git@git.trivento.nl:john/bier.git master:master [INFO] Working directory: /Users/johntenden/projecten/git/bier/indirectory [INFO] Release preparation complete. [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 18.936 s [INFO] Finished at: 2014-04-11T09:42:49+01:00 [INFO] Final Memory: 10M/156M
          Hide
          Robert Scholte added a comment -

          please surround the output with {noformat} tags to make it easier to read. Maybe I'm a bad reader, but I only see succeeding builds...

          Show
          Robert Scholte added a comment - please surround the output with {noformat} tags to make it easier to read. Maybe I'm a bad reader, but I only see succeeding builds...
          Hide
          john ten Den added a comment - - edited

          added {} markt in my first comment where I expected other behaviour.

          Show
          john ten Den added a comment - - edited added {} markt in my first comment where I expected other behaviour.
          Hide
          Robert Scholte added a comment -

          The root cause should be searched in the SCM project. SCM-740 also describes a problem with Git 1.9, but it exposes another problem, but it could be very well related.

          Show
          Robert Scholte added a comment - The root cause should be searched in the SCM project. SCM-740 also describes a problem with Git 1.9, but it exposes another problem, but it could be very well related.
          Hide
          Matthias Nisius added a comment - - edited

          I have exactly the same problem

          git 1.9.2 and 2.5 release plugin.
          I will move my main pom.xml in the git root but this is a very strange error and it is very bad that the maven build claims to be successfully...

          Edit: I have moved the main pom.xml in the root git repo and it worked!
          So yes this bug does definitely exisit.

          Show
          Matthias Nisius added a comment - - edited I have exactly the same problem git 1.9.2 and 2.5 release plugin. I will move my main pom.xml in the git root but this is a very strange error and it is very bad that the maven build claims to be successfully... Edit: I have moved the main pom.xml in the root git repo and it worked! So yes this bug does definitely exisit.
          Hide
          Alejandro added a comment -

          Same problem.
          Just wanted to add that I downgraded the plugin to 2.4.2 to try to fix the issue but had another problem

          org.apache.maven.scm.ScmException: Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

          So basically there is no workaround if you don't have the option of moving the pom to the root, it seems.

          Show
          Alejandro added a comment - Same problem. Just wanted to add that I downgraded the plugin to 2.4.2 to try to fix the issue but had another problem org.apache.maven.scm.ScmException: Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref So basically there is no workaround if you don't have the option of moving the pom to the root, it seems.
          Hide
          Martin Ellis added a comment -

          In case it helps anyone, I am currently working around this as follows:

          • Use maven-release-plugin version 2.4.2
          • Ensure git output is English
          • Set git's status.displayCommentPrefix configuration property to true (see below)

          I've set the displayCommentPrefix option in the .gitconfig of the user running release:prepare as follows:

          [status]
            displayCommentPrefix = true
          

          I haven't looked into whether there's a similar workaround for 2.5(.x) yet.

          Also, I haven't seen the "ref HEAD is not a symbolic ref" error reported by Alejandro E.

          Show
          Martin Ellis added a comment - In case it helps anyone, I am currently working around this as follows: Use maven-release-plugin version 2.4.2 Ensure git output is English Set git's status.displayCommentPrefix configuration property to true (see below) I've set the displayCommentPrefix option in the .gitconfig of the user running release:prepare as follows: [status] displayCommentPrefix = true I haven't looked into whether there's a similar workaround for 2.5(.x) yet. Also, I haven't seen the "ref HEAD is not a symbolic ref" error reported by Alejandro E.
          Hide
          Alexander Klimetschek added a comment - - edited

          Same issue here, with git 1.8.5.2 or 1.9.3 or 2.0.0 plus maven-release-plugin 2.5.

          Show
          Alexander Klimetschek added a comment - - edited Same issue here, with git 1.8.5.2 or 1.9.3 or 2.0.0 plus maven-release-plugin 2.5.
          Hide
          Alexander Klimetschek added a comment - - edited

          Issue with untracked files in git status --porcelain output

          One problem (but not the only one) is in those lines:

          [WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/pom.xml.releaseBackup
          [WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/release.properties
          

          These prevent the git commit from happening - WARNING here is an understatement, it should be ERROR since the execution is aborted and with no commit the following steps won't work

          The issue is that apparently in some git version the output of git status --porcelain changed to show untracked files using the ?? markers, and this will hit the 2 files that the maven release always creates, pom.xml.releaseBackup release.properties.

          From what I can see the problem was actually just recently introduced by SCM-709 (scm 1.9, maven-release-plugin 2.5 afaik) and commit fa5b0dd8 which made it fail on unknown lines (such as ??) instead of ignoring it as before.

          So one can fix that by telling git to not output any untracked files (??) by setting the git config status.showUntrackedFiles = no.

          *However*, after doing so, those WARNING lines are gone (good), but still the git commit doesn't happen (bad). Something else must make the scm plugin think there is no change to the pom.xml and not execute the commit (did not dig deeper).

          Workaround

          What worked for me was going back to an older release plugin, as @Martin Ellis above did:

          • git 2.0.0
          • release plugin 2.3.2 (did not try other versions)
          • git config: status.displayCommentPrefix = true (changed in git 1.8.5, afaiu that's what the release plugin 2.5 tries to fix)
          git config status.displayCommentPrefix true
          mvn org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare
          mvn org.apache.maven.plugins:maven-release-plugin:2.3.2:perform
          
          Show
          Alexander Klimetschek added a comment - - edited Issue with untracked files in git status --porcelain output One problem (but not the only one) is in those lines: [WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/pom.xml.releaseBackup [WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/release.properties These prevent the git commit from happening - WARNING here is an understatement, it should be ERROR since the execution is aborted and with no commit the following steps won't work The issue is that apparently in some git version the output of git status --porcelain changed to show untracked files using the ?? markers, and this will hit the 2 files that the maven release always creates, pom.xml.releaseBackup release.properties . From what I can see the problem was actually just recently introduced by SCM-709 (scm 1.9, maven-release-plugin 2.5 afaik) and commit fa5b0dd8 which made it fail on unknown lines (such as ??) instead of ignoring it as before. So one can fix that by telling git to not output any untracked files (??) by setting the git config status.showUntrackedFiles = no . * However *, after doing so, those WARNING lines are gone (good), but still the git commit doesn't happen (bad). Something else must make the scm plugin think there is no change to the pom.xml and not execute the commit (did not dig deeper). Workaround What worked for me was going back to an older release plugin, as @Martin Ellis above did: git 2.0.0 release plugin 2.3.2 (did not try other versions) git config: status.displayCommentPrefix = true (changed in git 1.8.5, afaiu that's what the release plugin 2.5 tries to fix) git config status.displayCommentPrefix true mvn org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare mvn org.apache.maven.plugins:maven-release-plugin:2.3.2:perform
          Hide
          Dominik Bartholdi added a comment -

          same issue with maven-release-plugin 2.5 and the jgit provider 1.9

          only moving the pom.xml to the root of the repo solves the issue

          Show
          Dominik Bartholdi added a comment - same issue with maven-release-plugin 2.5 and the jgit provider 1.9 only moving the pom.xml to the root of the repo solves the issue
          Hide
          Dominik Bartholdi added a comment -
          Show
          Dominik Bartholdi added a comment - placed a PR to fix this: https://github.com/apache/maven-scm/pull/17
          Hide
          Torben Knerr added a comment -

          workaround above git config --add status.displayCommentPrefix true did not work for me with Git 1.9.1 and release plugin 2.4.2

          Show
          Torben Knerr added a comment - workaround above git config --add status.displayCommentPrefix true did not work for me with Git 1.9.1 and release plugin 2.4.2
          Hide
          Martin Ellis added a comment -

          Torben: If you run maven with the -X option, it'll show the output of the git status command in the log. That way you'll be able to verify whether the comment prefix is being added.

          The regular expressions the git output is being matched against are the static fields in this class:

          http://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.7/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/status/GitStatusConsumer.java

          Show
          Martin Ellis added a comment - Torben: If you run maven with the -X option, it'll show the output of the git status command in the log. That way you'll be able to verify whether the comment prefix is being added. The regular expressions the git output is being matched against are the static fields in this class: http://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.7/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/status/GitStatusConsumer.java
          Hide
          Benson Margulies added a comment -

          See https://gist.github.com/bimargulies/c82594b0b57f6ab19c51.

          These are logs and such from https://github.com/bimargulies/pom-file-name-tc.git. To use this, make a clone where you can write tags, cd to the 'second' directory, and run 'mvn release:prepare'.

          You will get no commits, no errors, and a useless tag.

          Note that it has repository declarations for a Unix/MacOSX repo to deliver to; this probably does not matter for release:prepare. Note that this has a .gitignore that covers release.properties and pom.xml.releaseBackup, so clearly the problem is not git status yelping about those.

          Show
          Benson Margulies added a comment - See https://gist.github.com/bimargulies/c82594b0b57f6ab19c51 . These are logs and such from https://github.com/bimargulies/pom-file-name-tc.git . To use this, make a clone where you can write tags, cd to the 'second' directory, and run 'mvn release:prepare'. You will get no commits, no errors, and a useless tag. Note that it has repository declarations for a Unix/MacOSX repo to deliver to; this probably does not matter for release:prepare. Note that this has a .gitignore that covers release.properties and pom.xml.releaseBackup, so clearly the problem is not git status yelping about those.
          Hide
          Benson Margulies added a comment -

          This bug is already fixed in MAVEN-SCM! If I use the current snapshot, all is well. So I guess it's time to play release manager for maven-scm, and then for the release plugin.

          Show
          Benson Margulies added a comment - This bug is already fixed in MAVEN-SCM! If I use the current snapshot, all is well. So I guess it's time to play release manager for maven-scm, and then for the release plugin.
          Hide
          Benson Margulies added a comment -

          A series of experiments, using Linux and git 1.8.5.2:

          First, with .gitignore containing

          pom.xml.releaseBackup
          release.properties
          

          and version 2.5 of this plugin, I get the failure.

          Show
          Benson Margulies added a comment - A series of experiments, using Linux and git 1.8.5.2: First, with .gitignore containing pom.xml.releaseBackup release.properties and version 2.5 of this plugin, I get the failure.
          Hide
          Benson Margulies added a comment -

          second: changing only to a version of this plugin using SCM 1.9.1, all is well.

          Show
          Benson Margulies added a comment - second: changing only to a version of this plugin using SCM 1.9.1, all is well.
          Hide
          Benson Margulies added a comment -

          Third: remove the .gitignore coverage for release.properties and pom.xml.releaseBackup

          It still works fine.

          So I think that there is another problem lurking here. I will try an even newer git and see if I can expose it.

          Show
          Benson Margulies added a comment - Third: remove the .gitignore coverage for release.properties and pom.xml.releaseBackup It still works fine. So I think that there is another problem lurking here. I will try an even newer git and see if I can expose it.
          Hide
          Benson Margulies added a comment -

          Fourth: switch to git 1.9.2. Everything (with scm 1.9.1) is still fine.

          Show
          Benson Margulies added a comment - Fourth: switch to git 1.9.2. Everything (with scm 1.9.1) is still fine.
          Hide
          Benson Margulies added a comment -

          Fifth: git 2.1.0. Still works fine. prints:

          [WARNING] Ignoring unrecognized line: ?? second/pom.xml.releaseBackup
          [WARNING] Ignoring unrecognized line: ?? second/release.properties
          

          but correctly commits.

          So I have no clue what was going on that led to the pull request over in the SCM project.

          Show
          Benson Margulies added a comment - Fifth: git 2.1.0. Still works fine. prints: [WARNING] Ignoring unrecognized line: ?? second/pom.xml.releaseBackup [WARNING] Ignoring unrecognized line: ?? second/release.properties but correctly commits. So I have no clue what was going on that led to the pull request over in the SCM project.
          Hide
          Benson Margulies added a comment -

          I have also tried this with mvn -f, and also with two levels of directory, and it still declines to fail with scm 1.9.1. Anyone else want me to try anything else?

          Show
          Benson Margulies added a comment - I have also tried this with mvn -f, and also with two levels of directory, and it still declines to fail with scm 1.9.1. Anyone else want me to try anything else?
          Hide
          Benson Margulies added a comment -

          I can no longer reproduce this, even with -f, with SCM 1.9.2 integrated.

          Show
          Benson Margulies added a comment - I can no longer reproduce this, even with -f, with SCM 1.9.2 integrated.
          Hide
          Alexander Klimetschek added a comment - - edited

          How would you recommend to bring in maven-scm 1.9.2 (you are talking about maven-scm, right)? AFAICS, a normal maven pom setup would just depend on the maven-release-plugin, which itself only depends on maven-scm-api (1.9 in the latest released maven-release-plugin 2.5 from January). Not sure how maven-scm is pulled in normally.

          Would you add it as dependency to the maven-release-plugin like this (in e.g. a parent pom)?

          <plugin>
              <groupId>org.apache.maven.plugins</groupId>
              <artifactId>maven-release-plugin</artifactId>
              <version>2.5</version>
              <dependencies>
                  <dependency>
                      <groupId>org.apache.maven.scm</groupId>
                      <artifactId>maven-scm</artifactId>
                      <version>1.9.2</version>
                  </dependency>
              </dependencies>
              <configuration>
                  <!-- configs ... -->
              </configuration>
          </plugin>
          
          Show
          Alexander Klimetschek added a comment - - edited How would you recommend to bring in maven-scm 1.9.2 (you are talking about maven-scm, right)? AFAICS, a normal maven pom setup would just depend on the maven-release-plugin, which itself only depends on maven-scm-api (1.9 in the latest released maven-release-plugin 2.5 from January). Not sure how maven-scm is pulled in normally. Would you add it as dependency to the maven-release-plugin like this (in e.g. a parent pom)? <plugin> <groupId> org.apache.maven.plugins </groupId> <artifactId> maven-release-plugin </artifactId> <version> 2.5 </version> <dependencies> <dependency> <groupId> org.apache.maven.scm </groupId> <artifactId> maven-scm </artifactId> <version> 1.9.2 </version> </dependency> </dependencies> <configuration> <!-- configs ... --> </configuration> </plugin>
          Hide
          Alexander Klimetschek added a comment -

          Update: this was the solution, based on SCM-740:

          <plugin>
              <groupId>org.apache.maven.plugins</groupId>
              <artifactId>maven-release-plugin</artifactId>
              <version>2.5</version>
              <dependencies>
                  <dependency>
                      <groupId>org.apache.maven.scm</groupId>
                      <artifactId>maven-scm-provider-gitexe</artifactId>
                      <version>1.9.1</version>
                  </dependency>
              </dependencies>
              <configuration>
                  <!-- configs ... -->
              </configuration>
          </plugin>
          
          Show
          Alexander Klimetschek added a comment - Update: this was the solution, based on SCM-740 : <plugin> <groupId> org.apache.maven.plugins </groupId> <artifactId> maven-release-plugin </artifactId> <version> 2.5 </version> <dependencies> <dependency> <groupId> org.apache.maven.scm </groupId> <artifactId> maven-scm-provider-gitexe </artifactId> <version> 1.9.1 </version> </dependency> </dependencies> <configuration> <!-- configs ... --> </configuration> </plugin>

            People

            • Assignee:
              Benson Margulies
              Reporter:
              john ten Den
            • Votes:
              16 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development