[
https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=344681#comment-344681
]
Robert Scholte commented on MRELEASE-875:
-----------------------------------------
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?
> release:prepare does not commit pom.xml if not in the git root
> --------------------------------------------------------------
>
> Key: MRELEASE-875
> URL: https://jira.codehaus.org/browse/MRELEASE-875
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.5
> Environment: git 1.9.0
> Reporter: john ten Den
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
