[
https://issues.apache.org/jira/browse/SCM-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961351#comment-17961351
]
ASF GitHub Bot commented on SCM-412:
------------------------------------
jira-importer opened a new issue, #628:
URL: https://github.com/apache/maven-scm/issues/628
**[svarog](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=svarog)**
opened
**[SCM-412](https://issues.apache.org/jira/browse/SCM-412?redirect=false)** and
commented
When upgraded svn client from 1.5.0-dev to 1.5.2 the _mvn release:prepare_
fails:
```
[INFO] Executing: svn --non-interactive commit --file
C:\DOCUME~1\borutb\LOCALS~1\Temp\maven-scm-2091962435.commit --targets
C:\DOCUME~1\borutb\L
OCALS~1\Temp\maven-scm-44156-targets
[INFO] Working directory: C:\workarea\madserver-RB-1.3
[INFO] Tagging release with the label REL-1.3.10...
[INFO] Executing: svn --non-interactive copy --file
C:\DOCUME~1\borutb\LOCALS~1\Temp\maven-scm-855569361.commit .
https://svn.acme.com/repos
itories/modules/madserver/tags/REL-1.3.10
[INFO] Working directory: C:\workarea\madserver-RB-1.3
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Commit failed (details follow):
svn: File
'/repositories/modules/madserver/tags/REL-1.3.10/.settings/org.maven.ide.eclipse.prefs'
already exists
```
The same happens with 1.5.1 svn client on Linux with my coworker. Installing
1.5.0 solves the problem. As temporary files (.commit) are deleted I can not
give more details.
---
**Affects:** 1.0
**Issue Links:**
- [SCM-406](https://issues.apache.org/jira/browse/SCM-406) scm tag does not
work with Subversion 1.5.1
(_**"duplicates"**_)
> Preparing release fails with svn client 1.5.1 and 1.5.2
> -------------------------------------------------------
>
> Key: SCM-412
> URL: https://issues.apache.org/jira/browse/SCM-412
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: Maven version: 2.0.9
> Java version: 1.5.0_11
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Subversion command-line client, version 1.5.2
> Reporter: svarog
> Priority: Blocker
>
> When upgraded svn client from 1.5.0-dev to 1.5.2 the _mvn release:prepare_
> fails:
> {code}[INFO] Executing: svn --non-interactive commit --file
> C:\DOCUME~1\borutb\LOCALS~1\Temp\maven-scm-2091962435.commit --targets
> C:\DOCUME~1\borutb\L
> OCALS~1\Temp\maven-scm-44156-targets
> [INFO] Working directory: C:\workarea\madserver-RB-1.3
> [INFO] Tagging release with the label REL-1.3.10...
> [INFO] Executing: svn --non-interactive copy --file
> C:\DOCUME~1\borutb\LOCALS~1\Temp\maven-scm-855569361.commit .
> https://svn.acme.com/repos
> itories/modules/madserver/tags/REL-1.3.10
> [INFO] Working directory: C:\workarea\madserver-RB-1.3
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Unable to tag SCM
> Provider message:
> The svn tag command failed.
> Command output:
> svn: Commit failed (details follow):
> svn: File
> '/repositories/modules/madserver/tags/REL-1.3.10/.settings/org.maven.ide.eclipse.prefs'
> already exists
> {code}
> The same happens with 1.5.1 svn client on Linux with my coworker. Installing
> 1.5.0 solves the problem. As temporary files (.commit) are deleted I can not
> give more details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
