[
https://issues.apache.org/jira/browse/SCM-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15991436#comment-15991436
]
Richard DiCroce commented on SCM-807:
-------------------------------------
It's been quite a while now since I wrote this patch, but if memory serves,
that block of code was there to sort out which files are actually tracked by
Git in order to filter the list of returned files so that it only contains
files that were really added instead of ALL files in that directory (and
subdirectories). That is now handled by the block of code I added above the
loop, right under the comment {code}// we may have tried to add files covered
by .gitignore (so they weren't actually added){code}
> 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)
