[
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
