maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SCM-807) JGit impl check-in fails unless the Maven project is in the working copy root
Date Sat, 29 Apr 2017 11:41:04 GMT

    [ 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)

Mime
View raw message