[
https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348740#comment-348740
]
Martin Ellis commented on MRELEASE-875:
---------------------------------------
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:
{noformat}
[status]
displayCommentPrefix = true
{noformat}
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.
> 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)
