You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2016/05/30 21:45:13 UTC

[jira] [Commented] (SCM-807) JGit impl check-in fails unless the Maven project is in the working copy root

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

Robert Scholte commented on SCM-807:
------------------------------------

Looks to me like the {{add.call()}} now simply adds all files instead of respecting the filepatterns. I don't think that's correct.

> 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-git
>    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.4#6332)