[ http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157591#action_157591 ]
Al Robertson commented on SCM-406: ---------------------------------- Following up Johannes's rant... this IS a real problem for us too! Can I assume everyone else using Maven/Subversion has not upgraded to 1.5.x? Otherwise - not using the release plugin. I guess I thought it would be effecting more people than the 55 voters. We have a server running 1.4.x specifically for releasing at the moment. It also means we can't upgrade the subversion repos to 1.5 until this is fixed. I know the answer - fix it yourself. I just felt I needed to comment on this one because it's stopping us using svn 1.5. > scm tag does not work with Subversion 1.5.1 > ------------------------------------------- > > Key: SCM-406 > URL: http://jira.codehaus.org/browse/SCM-406 > 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: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira