maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Tran (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MRELEASE-409) SVN tag commit fails with "File ... already exists" error
Date Sat, 31 Jan 2009 04:15:19 GMT

     [ http://jira.codehaus.org/browse/MRELEASE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dan Tran closed MRELEASE-409.
-----------------------------

    Resolution: Won't Fix

see http://jira.codehaus.org/browse/SCM-406



> SVN tag commit fails with "File ... already exists" error
> ---------------------------------------------------------
>
>                 Key: MRELEASE-409
>                 URL: http://jira.codehaus.org/browse/MRELEASE-409
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-7
>         Environment: Maven version: 2.0.9
> Java version: 1.6.0_10
> OS name: "linux" version: "2.6.27-9-generic" arch: "amd64" Family: "unix"
>            Reporter: Philippe Laflamme
>
> Exexuting mvn release:prepare fails when trying to commit the tag. Executing svn update
and re-executing mvn release:prepare bypasses the problem. This is reported here:
> http://weblogs.java.net/blog/johnsmart/archive/2008/12/subversion_mave.html
> Here is the relevant maven output:
> # mvn release:prepare
> [...]
>         [INFO] Checking in modified POMs...
> [INFO] Executing: svn --non-interactive commit --file /tmp/maven-scm-625630017.commit
--targets /tmp/maven-scm-54523-targets
> [INFO] Working directory: /home/philippe/projects/obiba-commons
> [INFO] Tagging release with the label 1.0.2...
> [INFO] Executing: svn --non-interactive copy --file /tmp/maven-scm-1769870399.commit
. https://svn.obiba.org/obiba-commons/tags/releases/1.0.2
> [INFO] Working directory: /home/philippe/projects/obiba-commons
> [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 '/obiba-commons/tags/releases/1.0.2/obiba-core/pom.xml' already exists
> [INFO] ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 32 seconds
> [INFO] Finished at: Fri Jan 30 21:15:43 EST 2009
> [INFO] Final Memory: 15M/183M
> [INFO] ------------------------------------------------------------------------
> # svn update
> At revision 2311.
> # mvn release:prepare
> [...]
> [INFO] Resuming release from phase 'scm-tag'
> [INFO] Tagging release with the label 1.0.2...
> [INFO] Executing: svn --non-interactive copy --file /tmp/maven-scm-1384014558.commit
. https://svn.obiba.org/obiba-commons/tags/releases/1.0.2
> [INFO] Working directory: /home/philippe/projects/obiba-commons
> [INFO] Transforming 'Obiba Commons parent POM'...
> [INFO] Updating obiba-core to 1.0.3-SNAPSHOT
> [INFO] Ignoring artifact version update for expression: ${project.version}
> [INFO] Transforming 'Obiba Core'...
> [INFO] Transforming 'Obiba Wicket'...
> [INFO] Updating obiba-core to 1.0.3-SNAPSHOT
> [INFO] Not removing release POMs
> [INFO] Checking in modified POMs...
> [INFO] Executing: svn --non-interactive commit --file /tmp/maven-scm-1031237436.commit
--targets /tmp/maven-scm-51509-targets
> [INFO] Working directory: /home/philippe/projects/obiba-commons
> [INFO] Release preparation complete.
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 6 seconds
> [INFO] Finished at: Fri Jan 30 21:19:39 EST 2009
> [INFO] Final Memory: 15M/183M
> [INFO] ------------------------------------------------------------------------

-- 
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

        

Mime
View raw message