Bradley Baetz created MRELEASE-885:
--------------------------------------
Summary: When the base pom is a subdirectory, tagging fails in GIT
Key: MRELEASE-885
URL: https://jira.codehaus.org/browse/MRELEASE-885
Project: Maven Release Plugin
Issue Type: Bug
Components: Git, scm
Affects Versions: 2.5, 2.3.2
Environment: linux (fedora 20)
Reporter: Bradley Baetz
(NOTE, this is not the same as MRELEASE-875. I think)
Given a GIT checkout with a project structure of:
project/
dir1/pom.xml
dir2/pom.xml
Given an <scm> config of:
<developerConnection>scm:git:ssh://[email protected]:bbaetz/maven-release-bug.git</developerConnection>
the maven-release plugin correctly commits the pom file, but fails to tag. The
problem is that its stripping off one level of the URL, and doing:
[INFO] Executing: /bin/sh -c cd /home/bbaetz/src/subdir-project && git push
ssh://[email protected]:bbaetz refs/tags/project-1.0.0
which is wrong for git
To reproduce, fork https://github.com/bbaetz/maven-release-bug/, change the scm
settings to your own, and run:
mvn -X -B -f build/pom.xml -DdevelopmentVersion=1.0.1-SNAPSHOT
-DreleaseVersion=1.0.0 -Dresume=false release:prepare release:perform
I've tried various combinations of maven-release-plugin and maven-scm-plugin
versions, with no luck
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
