[
https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347627#comment-347627
]
Alejandro E commented on MRELEASE-875:
--------------------------------------
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
bq. 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.
> 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)
