maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alison Winters (JIRA)" <>
Subject [jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
Date Mon, 29 Sep 2008 04:11:45 GMT


Alison Winters commented on SCM-406:

This does appear to be an SVN "bug" in the sense that it doesn't let you tag from a non-head
revision, even if all the files in and below the current directory are in fact at the latest
revision for that directory on the repository.  I think perhaps Maven should hide this by
explicitly running an svn up prior to the svn copy - it makes sense anyways because presumably
you do always want to release from the head version of what's in the repository.

> scm tag does not work with Subversion 1.5.1
> -------------------------------------------
>                 Key: SCM-406
>                 URL:
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-svn
>    Affects Versions: 1.0
>            Reporter: James William Dumay
>             Fix For: 1.1.1
> scm:checkin does not work with Subversion 1.5.1
> On release:perform (which I assume calls scm:checkin) the following error occurs:
> {code}
> svn: File '/svn/private/atlassian/confluence/tags/confluence-project-2.10-m1/conf-acceptance-test/pom.xml'
already exists
> {code}
> Using subversion 1.4.x is a good enough workaround.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message