continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael K (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (CONTINUUM-2223) Release fails while creating SCM-TAG for module of a multi module project
Date Fri, 08 May 2009 09:42:44 GMT
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.3.2, 1.2.3
         Environment: Continuum 1.3.2 running on WindowsXP 
Installations: Maven 2.1.0, jdk1.6.0, 
            Reporter: Michael K


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

        

Mime
View raw message