[
https://issues.apache.org/jira/browse/SCM-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963192#comment-17963192
]
ASF GitHub Bot commented on SCM-807:
------------------------------------
jira-importer opened a new issue, #1037:
URL: https://github.com/apache/maven-scm/issues/1037
**[Richard
DiCroce](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rcd)**
opened
**[SCM-807](https://issues.apache.org/jira/browse/SCM-807?redirect=false)** and
commented
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.
---
**Affects:** 1.9.4
**Attachments:**
-
[scm-807.txt](https://issues.apache.org/jira/secure/attachment/12772861/scm-807.txt)
(_4.46 kB_)
**Issue Links:**
- [SCM-860](https://issues.apache.org/jira/browse/SCM-860) add goal creates
creates wrong paths if parent pom is not at root directory
(_**"is duplicated by"**_)
- [SCM-932](https://issues.apache.org/jira/browse/SCM-932) JGit does not
commit files in fileset based in subfolder
(_**"is duplicated by"**_)
- [SCM-990](https://issues.apache.org/jira/browse/SCM-990) Jgit Provider
cannot resolve Repository in multi-module Maven Project
(_**"is duplicated by"**_)
- [SCM-845](https://issues.apache.org/jira/browse/SCM-845) Maven Release
Plugin releases SNAPSHOT instead of STABLE version (jgit)
- [SCM-998](https://issues.apache.org/jira/browse/SCM-998) Streamline file
separator used in ScmFile.getPath()
(_**"Testing discovered"**_)
**Remote Links:**
- [GitHub Pull Request #152
](https://github.com/apache/maven-scm/pull/152)
- [GitHub Pull Request #158
](https://github.com/apache/maven-scm/pull/158)
1 votes, 7 watchers
> JGit impl check-in fails unless the Maven project is in the working copy root
> -----------------------------------------------------------------------------
>
> Key: SCM-807
> URL: https://issues.apache.org/jira/browse/SCM-807
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.9.4
> Reporter: Richard DiCroce
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 2.0.0-M2
>
> Attachments: scm-807.txt
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
