[ http://jira.codehaus.org/browse/CONTINUUM-170?page=comments#action_40279
]
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).
java.lang.NullPointerException
at
org.apache.maven.continuum.scm.DefaultContinuumScm.convertUpdateScmResult(DefaultContinuumScm.java:213)
at
org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:144)
at
org.apache.maven.continuum.buildcontroller.DefaultBuildController.update(DefaultBuildController.java:194)
at
org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:139)
at
org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:50)
at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:100)
at java.lang.Thread.run(Thread.java:534)
> project can get stuck in the updating state
> -------------------------------------------
>
> Key: CONTINUUM-170
> URL: http://jira.codehaus.org/browse/CONTINUUM-170
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
