continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bj?rn Sk?ld (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-170) project can get stuck in the updating state
Date Mon, 30 May 2005 15:11:22 GMT
     [ ]
Björn Sköld commented on CONTINUUM-170:

This occured to me too. Seems like scmResult.getUpdatedFiles() can return null in some scm
error cases (got this for a cvs repo).

        at org.apache.maven.continuum.scm.DefaultContinuumScm.convertUpdateScmResult(
        at org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(
        at org.apache.maven.continuum.buildcontroller.DefaultBuildController.update(
        at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(
        at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$

> project can get stuck in the updating state
> -------------------------------------------
>          Key: CONTINUUM-170
>          URL:
>      Project: Continuum
>         Type: Bug
>     Reporter: Brett Porter
>      Fix For: 1.0-alpha-3

> I don't have any diagnostic info on this (no idea where to look), but I had a project
get stuck in the update state that was irrecoverable (I couldn't even delete it, had to blow
away the whole db).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message