Maven SCM

scm:update with GIT sometimes fails to report the affected files

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 1.6
  • Fix Version/s: 1.7
  • Component/s: maven-scm-provider-git
  • Labels:
    None
  • Environment:
    git 1.7.5.4, mvn-3.0.4, OSX, Linux, locale de_AT
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

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.

Activity

People

  • Assignee:
    Mark Struberg
    Reporter:
    Mark Struberg
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: