[
https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351118#comment-351118
]
Martin Ellis commented on MRELEASE-875:
---------------------------------------
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
> 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, scm
> Affects Versions: 2.5
> Environment: git 1.9.0
> Reporter: john ten Den
> Assignee: Dominik Bartholdi
>
> 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)
