[ http://jira.codehaus.org/browse/CONTINUUM-656?page=comments#action_69543 ]
Dan Allen commented on CONTINUUM-656: ------------------------------------- I am also observing this issue. I have 8 modules underneath a single parent pom, which I am importing into continuum using the file:/ schema. Consistently, the first library is being duplicated upon import. However, I have been able to import project correctly without the duplicate (by being very methodical and patient). It appears that the duplicate is happening when I attempt to kickoff a build before continuum is finished checking out all the modules from SCM. There is some sort of race condition going on there. In addition to showing up twice, the entry has somehow violated a database constraint since any attempt to delete either of these duplicate modules leads to a stacktrace exception that cites a database contraint violation. > Child Project / Module added twice > ---------------------------------- > > Key: CONTINUUM-656 > URL: http://jira.codehaus.org/browse/CONTINUUM-656 > Project: Continuum > Type: Bug > Components: Web interface > Versions: 1.0.3 > Environment: Red Hat Enterprise Linux; Java 1.5 > Reporter: David H. DeWolf > Priority: Minor > > > Added parent project with 10 subprojects. Parent and all children were added > successfully. One of the modules was duplicated. Working to put together a > smaller test case. -- 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
