jira-importer commented on issue #592: URL: https://github.com/apache/maven-scm/issues/592#issuecomment-2964605719
**[David Moss](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dmosses)** commented > 3) Setting exportDirectory to an absoulte path, e.g. ${basedir}/target/export results in an error from svn saying that the directory already exists: > [INFO] Executing: svn --non-interactive export https://example.com/svn/theproject/trunk/ /home/havwig/theproject/leveranse/target/export > [INFO] Working directory: /home/havwig/theproject/leveranse/target/export > [ERROR] Provider message: > [ERROR] The svn command failed. > [ERROR] Command output: > [ERROR] svn: Destination directory exists; please remove the directory or use --force to overwrite > svn: '/home/havwig/theproject/leveranse/target/export' already exists Same problem here. This is a serious problem for me, with no apparent work around. If there were some way of passing the --force parameter to the svn command we could use that, but I can't see any provision for passing provider specific parameters through. Actually, what I need to achieve is merging two source trees - I'd hoped to export two projects into the same directory but obviously I'll need to be able to specify --force to do this. -- 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]
