[SCM-807] JGit impl check-in fails unless the Maven project is in the working copy root

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.9.4
• Fix Version/s: 2.0.0-M2
• Component/s: maven-scm-provider-gitexe
• Flags: Patch
• Assignee: Michael Osipov
• Reporter: Richard DiCroce
• Created: 17/Nov/15 22:51
• Updated: 28/Jul/22 18:26
• Resolved: 22/Jul/22 08:54

Description

Another problem exposed by maven-release-plugin: the JGit SCM implementation's check-in fails unless the Maven project is in the working copy root because it confuses the working copy's location with the Maven project's location.

The attached patch resolves the issue. Combined with the patch attached to SCM-806, release:prepare now mostly succeeds with the JGit implementation. There is still a problem with the POM not being transformed correctly, but that's a problem in maven-release-plugin.

Issue Links

• is duplicated by: SCM-860 add goal creates creates wrong paths if parent pom is not at root directory
• is duplicated by: SCM-932 JGit does not commit files in fileset based in subfolder
• is duplicated by: SCM-990 Jgit Provider cannot resolve Repository in multi-module Maven Project
• is related to: SCM-845 Maven Release Plugin releases SNAPSHOT instead of STABLE version (jgit)
• Testing discovered: SCM-998 Streamline file separator used in ScmFile.getPath()
• links to: GitHub Pull Request #152
• links to: GitHub Pull Request #158