continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wendy Smoak (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (CONTINUUM-1642) "Failed to rollback release" when no SNAPSHOT version was defined
Date Wed, 09 Sep 2009 21:01:31 GMT

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

Wendy Smoak updated CONTINUUM-1642:
-----------------------------------

    Fix Version/s: 1.x

> "Failed to rollback release" when no SNAPSHOT version was defined
> -----------------------------------------------------------------
>
>                 Key: CONTINUUM-1642
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1642
>             Project: Continuum
>          Issue Type: Bug
>          Components: Core system
>    Affects Versions: 1.1
>         Environment: OS: Linux
> Java: 1.5
>            Reporter: Martin Höller
>             Fix For: 1.x
>
>
> When you have a project without SNAPSHOT versions the release and rollback functionality
is broken. For example with our company POM we increment version whenever a change is done,
snapshots are never used. When I try to release a new version with continuum the release-prepare
fails, saying that no SNAPSHOT is defined. This could eventually be ok. But doing a rollback
afterwards freeces the web-UI with an TaskExecutionException in the logs:
> ERROR org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:rollback-release  - Error
executing task
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Failed to rollback release
>         at org.apache.maven.continuum.release.executors.RollbackReleaseTaskExecutor.execute(RollbackReleaseTaskExecutor.java:45)
>         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)
> Caused by: org.apache.maven.shared.release.ReleaseExecutionException: Cannot restore
from a missing backup POM: /srv/ci/continuum-1.1/apps/continuum/webapp/WEB-INF/working-director
> y/13/pom.xml.releaseBackup
>         at org.apache.maven.shared.release.phase.RestoreBackupPomsPhase.restorePomBackup(RestoreBackupPomsPhase.java:90)
>         at org.apache.maven.shared.release.phase.RestoreBackupPomsPhase.execute(RestoreBackupPomsPhase.java:69)
>         at org.apache.maven.shared.release.DefaultReleaseManager.rollback(DefaultReleaseManager.java:248)
>         at org.apache.maven.continuum.release.executors.RollbackReleaseTaskExecutor.execute(RollbackReleaseTaskExecutor.java:40)
>         ... 7 more

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