jira-importer commented on issue #887: URL: https://github.com/apache/maven-scm/issues/887#issuecomment-2964631347
**[Svend Hansen](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=svendhhh)** commented I've attached a patch. So, the fix is checking whether each file has an absolute path already, before prepending the working directory (and only doing so if they don't). I've changed the existing unit tests, to remove some of the hard coding, and added an extra test method to test the absolute path situation for both the edit and the checkin classes. Also, it turns out that it only breaks is the working directory exists, so I'm calling `new File(".").getAbsoluteFile()` to make sure it an existing directory, and to get files in there I do `new File("foo.xml").getAbsoluteFile()`. This is because if you have a directory `c:\foo` but not a directory `c:\bar`, then `new File("c:\foo\c:\foo\abc.xml` throws an IOException, while `new File("c:\bar\c:\bar.abc.xml` does NOT. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
