maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] (SCM-709) REGRESSION: git status doesn't work if repository root is not the working directory
Date Wed, 23 Jan 2013 18:13:13 GMT


Robert Scholte commented on SCM-709:

1. Although it looks like a hack, this will probably work. It's either knowing the relative
path between the workingdirectory and the repository root and check the actual file, or get
the information from the status-entries. Git claims that the output of porcelain is consistent.
After a chat with Mark we decided to try this. We have several different CI systems to verify
that this works. I would expect that the status-entry would already have enough information
to decide if the file exists or not.
2. That was another idea, but I'm pretty sure that it will break the tests right now.
3. Probably not. As a Windows user (probably the most critical OS in this case) I can confirm
that the GIT output is consistent and uses forward slashes.
4. Do we need to check if the file exists, if we better analyze the status output
5. See 4
6. That was my question to Mark
7. how?

Good point. AFAIK scm status expects all modified files inside (relative to?) the working
> REGRESSION: git status doesn't work if repository root is not the working directory
> -----------------------------------------------------------------------------------
>                 Key: SCM-709
>                 URL:
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-git
>    Affects Versions: 1.8, 1.8.1
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>            Priority: Blocker
> SCM-686 introduced the {{--porcelain}} option to make the {{status}} result language
> Without the {{--porcelain}} option files were listed relative to the working directory,
but with {{--porcelain}} files are listed relative to the repository root. In most cases these
are the same, but not always.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message