[prev in list] [next in list] [prev in thread] [next in thread] 

List:       maven-dev
Subject:    [jira] [Commented] (SCM-807) JGit impl check-in fails unless the Maven project is in the working cop
From:       "Michael Osipov (JIRA)" <jira () apache ! org>
Date:       2018-08-31 7:35:00
Message-ID: JIRA.12913907.1447800672000.201208.1535700900179 () Atlassian ! JIRA
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/SCM-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598370#comment-16598370 \
] 

Michael Osipov commented on SCM-807:
------------------------------------

Can someone provide a sample? I'd like to reproduce first and then apply the patch.

> 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
> Priority: Major
> 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
(v7.6.3#76005)


[prev in list] [next in list] [prev in thread] [next in thread]