Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Sat, 29 Apr 2017 11:41:04 +0000 (UTC)
From: "Konrad Windszus (JIRA)" <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.12913907.1447800672000.85181.1493466064061@Atlassian.JIRA>
In-Reply-To: <JIRA.12913907.1447800672000@Atlassian.JIRA>
References: <JIRA.12913907.1447800672000@Atlassian.JIRA> <JIRA.12913907.1447800672429@jira-lw-us.apache.org>
Subject: [jira] [Commented] (SCM-807) JGit impl check-in fails unless the
 Maven project is in the working copy root
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 29 Apr 2017 11:41:08 -0000


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

Konrad Windszus commented on SCM-807:
-------------------------------------

This patch works for me and fixes the issue described in SCM-845. Does anything speaks against committing it (except that there is no test for it)?

> 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
>         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
(v6.3.15#6346)