jira-importer commented on issue #629: URL: https://github.com/apache/maven-scm/issues/629#issuecomment-2964607786
**[Michael Johns](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=arabull)** commented I have a little color I can add to this discussion. We too use Maven, but I'm 99% sure this has nothing to do with it. Here's what I've done: 1. Ran a release in Maven; failed with the error everyone else is seeing (svn: File '...' already exists) 2. In a command prompt on our build box, changed to the project's working directory that was created by the Maven build. From there, ran a "svn --non-interactive copy -m \<message> . \<test destination>" manually (same command that Maven runs, save for an explicit message rather than --file). Got the same error. 2. Queried the working copy to see if any files were changed. No files were changed, but about 10 new files were present (relics from the aborted build). 3. Deleted the new files and ran the command again. Failed again with same error. 4. Ran an update on my working copy. No changes happened (no new files, deleted files, or changed files), but something happened because... 5. Ran the command again, and it worked. Some things to note: * We have a multi-module project. * We're on Windows Server 2003. * I installed SVN using various methods (msi, unzip), and they all fail. We have 1.5.2 with the Apache 2.0 bindings. * This problem doesn't happen with SVN 1.5.0, but it does happen with 1.5.1. To me, this most definitely appears to be a SVN bug. I've also posted this to the subversion users mailing list since it's really more relevant to them. But I figured I'd cross-post it here to help exonerate Maven as the culprit. -- 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
