Return-Path: Delivered-To: apmail-continuum-issues-archive@www.apache.org Received: (qmail 6030 invoked from network); 17 Nov 2009 18:40:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Nov 2009 18:40:26 -0000 Received: (qmail 450 invoked by uid 500); 17 Nov 2009 18:40:25 -0000 Delivered-To: apmail-continuum-issues-archive@continuum.apache.org Received: (qmail 406 invoked by uid 500); 17 Nov 2009 18:40:25 -0000 Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@continuum.apache.org Delivered-To: mailing list issues@continuum.apache.org Received: (qmail 396 invoked by uid 99); 17 Nov 2009 18:40:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Nov 2009 18:40:25 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [63.246.2.115] (HELO codehaus01.managed.contegix.com) (63.246.2.115) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Nov 2009 18:40:16 +0000 Received: from codehaus01.managed.contegix.com (localhost.localdomain [127.0.0.1]) by codehaus01.managed.contegix.com (Postfix) with ESMTP id 390DF1DE0112 for ; Tue, 17 Nov 2009 12:39:55 -0600 (CST) Date: Tue, 17 Nov 2009 12:39:55 -0600 (CST) From: "Michael K (JIRA)" To: issues@continuum.apache.org Message-ID: <23561019.13704.1258483195171.JavaMail.haus-jira@codehaus01.managed.contegix.com> In-Reply-To: <26151179.146151241775764910.JavaMail.haus-jira@codehaus01.managed.contegix.com> Subject: [jira] Closed: (CONTINUUM-2223) Release fails while creating SCM-TAG for module of a multi module project MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 4e90ceb663894a42f12c0e28abbab431 X-Virus-Checked: Checked by ClamAV on apache.org [ http://jira.codehaus.org/browse/CONTINUUM-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael K closed CONTINUUM-2223. -------------------------------- Resolution: Fixed I updated the svn-client on the build-server to sliksvn1.6.6. That helped. So the bug is fixed for me. > Release fails while creating SCM-TAG for module of a multi module project > ------------------------------------------------------------------------- > > Key: CONTINUUM-2223 > URL: http://jira.codehaus.org/browse/CONTINUUM-2223 > Project: Continuum > Issue Type: Bug > Components: Release > Affects Versions: 1.2.3, 1.3.2 > Environment: Continuum 1.3.2 running on WindowsXP > Installations: Maven 2.1.0, jdk1.6.0, > Reporter: Michael K > Fix For: Backlog > > > Release fails while creating SCM-TAG for module of a multi module project. I tried it first with continuum 1.2.3 and then with 1.3.2 with the same result. There seems to be the scm tag already exists, but before releasing was started, there was not such a tag. > [INFO] Multi Module Maven Demo ............................... SUCCESS [5.532s] > [INFO] Module1 ............................................... SUCCESS [8.125s] > [INFO] Module2 ............................................... SUCCESS [5.235s] > [INFO] ------------------------------------------------------------------------ > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD SUCCESSFUL > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 20 seconds > [INFO] Finished at: Fri May 08 11:12:21 CEST 2009 > [INFO] Final Memory: 35M/127M > [INFO] ------------------------------------------------------------------------ > [ERROR] org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to tag SCM > Provider message: > The svn tag command failed. > Command output: > svn: Commit failed (details follow): > svn: File '/svn/test_x/tags/MultiModuleMavenDemo-0.0.4/Module1/pom.xml' already exists > at org.apache.maven.shared.release.phase.ScmTagPhase.execute(ScmTagPhase.java:99) > at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194) > at org.apache.maven.shared.release.DefaultReleaseManager.prepareWithResult(DefaultReleaseManager.java:107) > at org.apache.maven.continuum.release.executors.PrepareReleaseTaskExecutor.execute(PrepareReleaseTaskExecutor.java:44) > at org.apache.maven.continuum.release.executors.AbstractReleaseTaskExecutor.executeTask(AbstractReleaseTaskExecutor.java:68) > at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116) > at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) > at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178) > at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) > at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) > at java.lang.Thread.run(Thread.java:619) -- 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