[
https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=352638#comment-352638
]
Benson Margulies commented on MRELEASE-875:
-------------------------------------------
See https://gist.github.com/bimargulies/c82594b0b57f6ab19c51.
These are logs and such from
https://github.com/bimargulies/pom-file-name-tc.git. To use this, make a clone
where you can write tags, cd to the 'second' directory, and run 'mvn
release:prepare'.
You will get no commits, no errors, and a useless tag.
Note that it has repository declarations for a Unix/MacOSX repo to deliver to;
this probably does not matter for release:prepare. Note that this has a
.gitignore that covers release.properties and pom.xml.releaseBackup, so clearly
the problem is _not_ git status yelping about those.
> 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)
