[SCM-375] Problems with svn export and <exportDirectory>

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0
• Fix Version/s: 1.2
• Component/s: maven-scm-provider-svn
• Environment: Maven 2.0.8 / Linux
• Assignee: Dan Tran
• Reporter: Håvard Wigtil
• Created: 22/Apr/08 02:59
• Updated: 11/Jan/09 03:27
• Resolved: 11/Jan/09 03:27

Description

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>

Issue Links

• relates to: SCM-432 Goal scm:export does not work for Subversion repository