jira-importer commented on issue #918: URL: https://github.com/apache/maven-scm/issues/918#issuecomment-2964632959
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented `@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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
