[ http://jira.codehaus.org/browse/CONTINUUM-660?page=comments#action_78821 ] Michael Semb Wever commented on CONTINUUM-660: ----------------------------------------------
To force delete these stale projects from continuum, (stop continuum and) log into derby and execute (where $1 = project_id): delete from PROJECT_NOTIFIERS where ID_OID = $1; delete from PROJECT_BUILDDEFINITIONS where ID_OID = $1; delete from PROJECTDEVELOPER where DEVELOPERS_ID_OWN = $1; delete from BUILDRESULT where PROJECT_ID_OID = $1; delete from PROJECTDEPENDENCY where DEPENDENCIES_ID_OWN = $1; delete from PROJECT where ID = $1; PS I've had corrupt projects happening in all sorts of ways, not just when adding projects. And have had to run the different statements at different times to ensure constraints are removed before executing the last line. If would be nice if continuum had a "force delete" button that did this for you on the delete confirmation page. > One or more module in a project is added twice during adding maven2 projects > ---------------------------------------------------------------------------- > > Key: CONTINUUM-660 > URL: http://jira.codehaus.org/browse/CONTINUUM-660 > Project: Continuum > Issue Type: Bug > Affects Versions: 1.0.3 > Environment: Solaris10 on sparc > Reporter: Kaare Nilsen > Fix For: 1.1 > > Attachments: stacktrace_when_delete.txt > > > In the latest rc when adding a project with multiple modules one or more of > the modules are added twice (duplicated). When this happens there is no way > of deleting one of them eighter so basicly you are stuck with one module > which always will have the "new" state and are never built. > I will attach some log showing what happens when I get to work in the morning -- 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
