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...@codehaus.org> on 2013/01/03 12:17:13 UTC
[jira] (SCM-709) REGRESSION: git status regexps invalid
Robert Scholte created SCM-709:
----------------------------------
Summary: REGRESSION: git status regexps invalid
Key: SCM-709
URL: https://jira.codehaus.org/browse/SCM-709
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-git
Affects Versions: 1.8.1, 1.8
Reporter: Robert Scholte
Priority: Blocker
SCM-686 introduced the {{--porcelain}} option to make the {{status}} result language independend.
The regular expressions have changed, but they are too wide, which might cause invalid matches.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository
root is not the working directory
Posted by "Darryl L. Miles (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317886#comment-317886 ]
Darryl L. Miles edited comment on SCM-709 at 1/23/13 4:13 PM:
--------------------------------------------------------------
@Tim
cd subdir/in/one/git/repo
git status --porcelain .
Note the use of the "." file name.
This can be used to get SVN like behaviour where only the files changes below the current directly are shown.
was (Author: dlmiles):
@Tim
cd subdir/in/one/git/repo
git status --porcelain .
can be used to get SVN like behaviour where only the files changes below the current directly are shown.
> REGRESSION: git status doesn't work if repository root is not the working directory
> -----------------------------------------------------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> 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 independend.
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository
root is not the working directory
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated SCM-709:
-------------------------------
Description:
SCM-686 introduced the {{--porcelain}} option to make the {{status}} result language independend.
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.
was:
SCM-686 introduced the {{--porcelain}} option to make the {{status}} result language independend.
The regular expressions have changed, but they are too wide, which might cause invalid matches.
Assignee: Robert Scholte
Summary: REGRESSION: git status doesn't work if repository root is not the working directory (was: REGRESSION: git status regexps invalid)
> REGRESSION: git status doesn't work if repository root is not the working directory
> -----------------------------------------------------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> 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 independend.
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository
root is not the working directory
Posted by "Andrei Pozolotin (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317873#comment-317873 ]
Andrei Pozolotin commented on SCM-709:
--------------------------------------
I just remembered that it worked fine with maven-release-plugin v 2.3.2 (and whatever SCM dependency was there)
is there easy way to see what specific change to v 2.4 (and related SCM) broke this?
> REGRESSION: git status doesn't work if repository root is not the working directory
> -----------------------------------------------------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> 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 independend.
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository
root is not the working directory
Posted by "Andrei Pozolotin (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317822#comment-317822 ]
Andrei Pozolotin commented on SCM-709:
--------------------------------------
I took a look. few ideas:
1) "/" feels like a hack; who guarantees its presence ?
2) could you differentiate via all of: File.exists() File.isFile() File.isDirectory() ?
3) "/" probably should be File.separator ?
4) need File.getCanonicalFile() to guard against symlinks ?
5) need File.getAbsolutePath() to actually render File.separator suffix ?
6) only one of oldFilePath or newFilePath is actually present on file system for File.exists() to work,
could be logic error in :: if ( status == ScmFileStatus.RENAMED ) {} :: block, if treating both same way ?
7) if original issue is path/file overlap, may be should detect specifically only that?
> REGRESSION: git status doesn't work if repository root is not the working directory
> -----------------------------------------------------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> 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 independend.
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository
root is not the working directory
Posted by "Andrei Pozolotin (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317801#comment-317801 ]
Andrei Pozolotin commented on SCM-709:
--------------------------------------
I am curious what next steps would be?
> REGRESSION: git status doesn't work if repository root is not the working directory
> -----------------------------------------------------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> 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 independend.
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status regexps invalid
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316545#comment-316545 ]
Robert Scholte commented on SCM-709:
------------------------------------
Reference: http://www.kernel.org/pub/software/scm/git/docs/git-status.html
> REGRESSION: git status regexps invalid
> --------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.8, 1.8.1
> Reporter: Robert Scholte
> Priority: Blocker
>
> SCM-686 introduced the {{--porcelain}} option to make the {{status}} result language independend.
> The regular expressions have changed, but they are too wide, which might cause invalid matches.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository
root is not the working directory
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317806#comment-317806 ]
Robert Scholte commented on SCM-709:
------------------------------------
My latest commit was https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=commitdiff;h=6aff3431817108139d29914dc81d8d2dc53e3c6a
The idea is to check for a forward slash at the end. If so, it should be a directory, otherwise a file.
But if I switch the lines of {{private boolean isFile( String file )}}, some tests fail.
The reason: if a file does not exist, it returns {{false}}, but that's not the same as being a directory.
Mark Struberg offered his help within a couple of weeks to check if the tests are wrong or not.
Or you could speed it up by having a look at it.
> REGRESSION: git status doesn't work if repository root is not the working directory
> -----------------------------------------------------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> 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 independend.
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository
root is not the working directory
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317868#comment-317868 ]
Robert Scholte commented on SCM-709:
------------------------------------
@Andrei:
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?
@Tim
Good point. AFAIK scm status expects all modified files inside (relative to?) the working directory.
> REGRESSION: git status doesn't work if repository root is not the working directory
> -----------------------------------------------------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> 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 independend.
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status regexps invalid
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316781#comment-316781 ]
Robert Scholte commented on SCM-709:
------------------------------------
from http://markmail.org/message/trozsqiym4zruj2u
{quote}
My git version is: 1.7.7.5 (Apple Git-26)
Here's a sample output of git status --porcelain:
M pom.xml
A foo-archetype/pom.xml
?? phonebook/
{quote}
As expected I would say...
> REGRESSION: git status regexps invalid
> --------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.8, 1.8.1
> Reporter: Robert Scholte
> Priority: Blocker
>
> SCM-686 introduced the {{--porcelain}} option to make the {{status}} result language independend.
> The regular expressions have changed, but they are too wide, which might cause invalid matches.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository
root is not the working directory
Posted by "Darryl L. Miles (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317886#comment-317886 ]
Darryl L. Miles commented on SCM-709:
-------------------------------------
@Tim
cd subdir/in/one/git/repo
git status --porcelain .
can be used to get SVN like behaviour where only the files changes below the current directly are shown.
> REGRESSION: git status doesn't work if repository root is not the working directory
> -----------------------------------------------------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> 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 independend.
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status regexps invalid
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317514#comment-317514 ]
Robert Scholte commented on SCM-709:
------------------------------------
Differences between --short and --porcelain:
{quote}
1. The users color.status configuration is not respected; color will always be off.
2. The users status.relativePaths configuration is not respected; paths shown will always be relative to the repository root.
{quote}
So this is actually saying that the working directory is ignored. And if the working directory is not the repository root, you're having an issue.
> REGRESSION: git status regexps invalid
> --------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.8, 1.8.1
> Reporter: Robert Scholte
> Priority: Blocker
>
> SCM-686 introduced the {{--porcelain}} option to make the {{status}} result language independend.
> The regular expressions have changed, but they are too wide, which might cause invalid matches.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository
root is not the working directory
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317874#comment-317874 ]
Robert Scholte commented on SCM-709:
------------------------------------
SCM-686 broke it
> REGRESSION: git status doesn't work if repository root is not the working directory
> -----------------------------------------------------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> 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 independend.
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status regexps invalid
Posted by "Tim Kettler (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317481#comment-317481 ]
Tim Kettler commented on SCM-709:
---------------------------------
The problem is not with the regex but with the processing afterwards.
{{GitStatusConsumer}} tries to construct a new File object from the {{workingDirectory}} and the extracted path from the regex and then checks for existence.
Values for me are:
{{workingDirectory}} = /home/tik/Develop/barchart-bugs/barchart-bugs-MRELEASE-812/build-tester/barchart-bugs-MRELEASE-812-case-02
{{files.get( 0 )}} = barchart-bugs-MRELEASE-812/build-tester/barchart-bugs-MRELEASE-812-case-02/pom.xml
Obviously, the paths overlap and hence the check fails and the file is discarded.
> REGRESSION: git status regexps invalid
> --------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.8, 1.8.1
> Reporter: Robert Scholte
> Priority: Blocker
>
> SCM-686 introduced the {{--porcelain}} option to make the {{status}} result language independend.
> The regular expressions have changed, but they are too wide, which might cause invalid matches.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository
root is not the working directory
Posted by "Tim Kettler (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317829#comment-317829 ]
Tim Kettler commented on SCM-709:
---------------------------------
I started looking into how to fix this yesterday, too. The most natural solution for me seemed to be to find the repository root and create the files based on that. Either by invoking {{git rev-parse --show-toplevel}} or by walking up the directory tree and looking for {{'.git'}}.
The other issue to consider is the actual semantics of the status command. Invoked from the repository root all provider implementations behave the same but from a subdirectory {{svn status}} only shows changes in the subdirectory and below while git shows changes from the whole repository. Is this intended or should the scm status command behave uniform regardless of the provider?
> REGRESSION: git status doesn't work if repository root is not the working directory
> -----------------------------------------------------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> 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 independend.
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status regexps invalid
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317511#comment-317511 ]
Robert Scholte commented on SCM-709:
------------------------------------
Now we seem to have to root cause. Still weird that only a few people seem to have trouble with it. The next question would be: which of the 2 values is wrong?
> REGRESSION: git status regexps invalid
> --------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.8, 1.8.1
> Reporter: Robert Scholte
> Priority: Blocker
>
> SCM-686 introduced the {{--porcelain}} option to make the {{status}} result language independend.
> The regular expressions have changed, but they are too wide, which might cause invalid matches.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-709) REGRESSION: git status doesn't work if repository
root is not the working directory
Posted by "Tim Kettler (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317912#comment-317912 ]
Tim Kettler commented on SCM-709:
---------------------------------
@Darryl
That's what the command should be changed to then.
> REGRESSION: git status doesn't work if repository root is not the working directory
> -----------------------------------------------------------------------------------
>
> Key: SCM-709
> URL: https://jira.codehaus.org/browse/SCM-709
> 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 independend.
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira