[
https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347433#comment-347433
]
Matthias Nisius edited comment on MRELEASE-875 at 6/3/14 8:25 AM:
------------------------------------------------------------------
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.
was (Author: daedalus23):
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 id worked!
So yes this bug does definitely exisit.
> 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)
