maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kyle Lebel (JIRA)" <>
Subject [jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
Date Thu, 27 Nov 2008 15:12:19 GMT


Kyle Lebel commented on SCM-406:

This is true.  My suggestion is flawed in a scenario where many developers risk committing
to the trunk while building tags.  In our situation, there are often many projects on the
go with a manageable amount of developers (2-5) working on them.  While building tags, we
communicate to them to not commit to the trunk until the release is completed.  

But obviously this does not cover all scenarios.  

> 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