[jira] Issue Comment Edited: (SCM-375) Problems with svn export and

["David Moss (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/SCM-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160345#action_160345 ] 

David Moss edited comment on SCM-375 at 1/8/09 3:04 AM:
--------------------------------------------------------

{quote}
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
{quote}

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 to achieve this, but obviously I'll need to be able to specify --force to achieve this.

      was (Author: dmosses):
    {quote}
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
{quote}

Same problem here.
  
> Problems with svn export and <exportDirectory>
> ----------------------------------------------
>
>                 Key: SCM-375
>                 URL: http://jira.codehaus.org/browse/SCM-375
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-svn
>    Affects Versions: 1.0
>         Environment: Maven 2.0.8 / Linux
>            Reporter: Håvard Wigtil
>
> The behaviour of <exportDirectory> for svn export seems buggy. I have three (probably related problems):
> 1) Not setting exportDirectory on export results in a NPE. I can understand that the setting is required, but I would expect an error message instead.
> 2) Setting exportDirectory to a relative path gets me this path twice, e.g. setting exportDirectory to target/export results in an export in target/export/target/export
> 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
> I use the configuration below:
> <plugin>
>     <artifactId>maven-scm-plugin</artifactId>
>     <version>1.0</version>
>     <configuration>
>         <connectionUrl>scm:svn:https://example.com/svn/theproject/trunk/ </connectionUrl>
>         <exportDirectory>${basedir}/target/export</exportDirectory>
>     </configuration>
>     <executions>
>         <execution>
>             <id>leveranse</id>
>             <phase>package</phase>
>             <goals>
>                 <goal>export</goal>
>             </goals>
>         </execution>
>     </executions>
> </plugin>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira