You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org> on 2011/07/17 03:22:43 UTC

[jira] Updated: (CONTINUUM-2166) Problem with release:prepare for a multimodule project using continuum

     [ https://jira.codehaus.org/browse/CONTINUUM-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Catherine Tan updated CONTINUUM-2166:
-------------------------------------------

    Fix Version/s:     (was: 1.4.1 (Beta))
                   1.4.2 (Beta)

> Problem with release:prepare for a multimodule project using continuum
> ----------------------------------------------------------------------
>
>                 Key: CONTINUUM-2166
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2166
>             Project: Continuum
>          Issue Type: Improvement
>    Affects Versions: 1.3.2 (Beta)
>         Environment: Linux, continuum, svn 1.5.2
>            Reporter: Lionel Champalaune
>             Fix For: 1.4.2 (Beta)
>
>
> I configured my release plugin as this in my project using the last 2.0 beta 9 release:
> 		<plugin>
> 			<groupId>org.apache.maven.plugins</groupId>
> 			<artifactId>maven-release-plugin</artifactId>
> 			<version>2.0-beta-9</version>
> 			<configuration>
> 				                    <remoteTagging>true</remoteTagging>
> 			</configuration>
> 		</plugin>
> My project look like this
> Project\
>             pom.xml
>             SubProject1\
>                            pom.xml
>                            ....
>             SubProject2\
>                            pom.xml
>                            ....
> Using continuum I prepared the release and I still have the error:
> [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/tags/Version/Project/SubProject1/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:43)
> 	at org.apache.maven.continuum.release.executors.AbstractReleaseTaskExecutor.executeTask(AbstractReleaseTaskExecutor.java:67)
> 	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:176)
> 	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> 	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> 	at java.lang.Thread.run(Thread.java:595)
> The Version repository doesn't not exist at the end
> Do I miss something with continuum and the new release plugin?
> It works well for single module (but it was already working with the previous release-plugin version)
> Is there an issue on that problem because it seems that the entire bugs related to svn > 1.5.0 are closed.
> Thanks 
> Regards
> Lionel

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira