[
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
