[MRELEASE-885] When the base pom is a subdirectory, tagging fails in GIT

• Type: Bug
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.3.2, 2.5
• Component/s: Git, scm
• Environment: linux (fedora 20)
• Assignee: Unassigned
• Reporter: Bradley Baetz
• Created: 25/Aug/14 02:49
• Updated: 01/Jul/24 11:44

Description

(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://[e-mail]: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://[e-mail]: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

Issue Links

• duplicates: MRELEASE-875 release:prepare does not commit pom.xml if not in the git root
• is duplicated by: MRELEASE-942 scm.url in release.properties incorrectly has project name appended if not defined in the top level pom