[
https://issues.apache.org/jira/browse/SCM-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570753#comment-17570753
]
ASF GitHub Bot commented on SCM-807:
------------------------------------
michael-o commented on PR #158:
URL: https://github.com/apache/maven-scm/pull/158#issuecomment-1193710147
> But `CheckInScmResult` always returns `ScmFile` with forward slashes (even
on Mercurial and Subversion)
Well, the we need to define the behavior for 2.0.0 and apply it in Maven
Release as well. It is up to us.
> 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
> 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)
