[
https://issues.apache.org/jira/browse/SCM-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962467#comment-17962467
]
ASF GitHub Bot commented on SCM-663:
------------------------------------
jira-importer opened a new issue, #872:
URL: https://github.com/apache/maven-scm/issues/872
**[Mark
Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)**
opened
**[SCM-663](https://issues.apache.org/jira/browse/SCM-663?redirect=false)** and
commented
I'm not sure if this is a change which got introduced in git-1.7.5 or if
it's only depending on a specific local setting. In any case git pull doesn't
always report the affected files. Thus we cannot parse it this way.
When executing the ScmUpdateTck, I get the following output
```
~$>cd
/Users/struberg/develop/java/apache/maven/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/target/scm-test/updating-copy
&& git pull
file:///Users/struberg/develop/java/apache/maven/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/target/scm-test/repository
master
remote: Counting objects: 14, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 9 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (9/9), done.
From
file:///Users/struberg/develop/java/apache/maven/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/target/scm-test/repository
* branch master -> FETCH_HEAD
First, rewinding head to replay your work on top of it...
Fast-forwarded master to fa61c64a494a5c4b28bc6211104982e35a970e1b.
```
In my case this is mostly caused by having specified the
branch.autosetuprebase on all my boxes. We would need to check if this is also
the case for our CI server on builds.apache.org.
---
**Affects:** 1.6
> scm:update with GIT sometimes fails to report the affected files
> -----------------------------------------------------------------
>
> Key: SCM-663
> URL: https://issues.apache.org/jira/browse/SCM-663
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.6
> Environment: git 1.7.5.4, mvn-3.0.4, OSX, Linux, locale de_AT
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Priority: Critical
> Fix For: 1.7
>
>
> I'm not sure if this is a change which got introduced in git-1.7.5 or if it's
> only depending on a specific local setting. In any case git pull doesn't
> always report the affected files. Thus we cannot parse it this way.
> When executing the ScmUpdateTck, I get the following output
> {noformat}
> ~$>cd
> /Users/struberg/develop/java/apache/maven/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/target/scm-test/updating-copy
> && git pull
> file:///Users/struberg/develop/java/apache/maven/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/target/scm-test/repository
> master
> remote: Counting objects: 14, done.
> remote: Compressing objects: 100% (4/4), done.
> remote: Total 9 (delta 0), reused 0 (delta 0)
> Unpacking objects: 100% (9/9), done.
> From
> file:///Users/struberg/develop/java/apache/maven/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/target/scm-test/repository
> * branch master -> FETCH_HEAD
> First, rewinding head to replay your work on top of it...
> Fast-forwarded master to fa61c64a494a5c4b28bc6211104982e35a970e1b.
> {noformat}
> In my case this is mostly caused by having specified the
> branch.autosetuprebase on all my boxes. We would need to check if this is
> also the case for our CI server on builds.apache.org.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
