[ http://jira.codehaus.org/browse/CONTINUUM-660?page=comments#action_69588 ]
Dan Allen commented on CONTINUUM-660: ------------------------------------- Please see CONTINUUM-656 for details. It is possible to not reproduce this problem. It all depends on your actions while importing the project. If you try to kick off a build before the checkout of the source is finished, bad data is getting inserted into the database. At this point, continuum is corrupt and you are forced to delete and start over. > 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 > Type: Bug > 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
