[
https://issues.apache.org/jira/browse/SCM-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961223#comment-17961223
]
ASF GitHub Bot commented on SCM-375:
------------------------------------
jira-importer opened a new issue, #592:
URL: https://github.com/apache/maven-scm/issues/592
**[Håvard
Wigtil](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=havwig)**
opened
**[SCM-375](https://issues.apache.org/jira/browse/SCM-375?redirect=false)** and
commented
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>
---
**Affects:** 1.0
**Issue Links:**
- [SCM-432](https://issues.apache.org/jira/browse/SCM-432) Goal scm:export
does not work for Subversion repository
> Problems with svn export and <exportDirectory>
> ----------------------------------------------
>
> Key: SCM-375
> URL: https://issues.apache.org/jira/browse/SCM-375
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Affects Versions: 1.0
> Environment: Maven 2.0.8 / Linux
> Reporter: Håvard Wigtil
> Assignee: Dan Tran
> Priority: Major
> Fix For: 1.2
>
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
