Return-Path: Delivered-To: apmail-continuum-users-archive@www.apache.org Received: (qmail 46731 invoked from network); 30 Jun 2008 13:50:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Jun 2008 13:50:19 -0000 Received: (qmail 39346 invoked by uid 500); 30 Jun 2008 13:50:19 -0000 Delivered-To: apmail-continuum-users-archive@continuum.apache.org Received: (qmail 39329 invoked by uid 500); 30 Jun 2008 13:50:19 -0000 Mailing-List: contact users-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@continuum.apache.org Delivered-To: mailing list users@continuum.apache.org Delivered-To: moderator for users@continuum.apache.org Received: (qmail 22871 invoked by uid 99); 30 Jun 2008 13:38:54 -0000 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApcAAGF+aEgK2xgL/2dsb2JhbAAIkXeeOA X-IronPort-AV: E=Sophos;i="4.27,727,1204498800"; d="scan'208";a="140629758" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: trying to delete project: JDO error Date: Mon, 30 Jun 2008 15:37:20 +0200 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: trying to delete project: JDO error Thread-Index: AcjarwLUFW7d+5/PSqagtoV1704EIAAAe8rgAACOwoAAADcsIAAAalRQ From: To: X-OriginalArrivalTime: 30 Jun 2008 13:37:21.0004 (UTC) FILETIME=[6BF2DAC0:01C8DAB6] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org I change the goal to "validate" before delete, then it's easy to force a su= ccessful build, because validate doesn't do much. If you still got problems= , try to delete all notifiers and build definitions (after the successful v= alidate build). I have often problems with delete, but it always work after= the procedure described above.=20 Odd=20 -----Original Message----- From: Lustig, Marc (Allianz Deutschland, externer Mitarbeiter) [mailto:EXTE= RN.LUSTIG_MARC@allianz.de]=20 Sent: 30. juni 2008 15:29 To: users@continuum.apache.org Subject: AW: trying to delete project: JDO error=20 yes, the last build failed. So, from the 100+ builds I deleted the latest o= nes which failed, so that the most recent build was a successfull one. Again I tried to delete the project, as a result, I still get the contrains= t-failure: javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM `PROJEC= T` WHERE `ID` =3D ? NestedThrowables: com.mysql.jdbc.exceptions.jdbc4.MySQL= IntegrityConstraintViolationException: Cannot delete or update a parent row= : a foreign key constraint fails (`continuum/BUILDRESULT`, CONSTRAINT `BUIL= DRESULT_FK3` FOREIGN KEY (`PROJECT_ID_OID`) REFERENCES `PROJECT` (`ID`)) =20 -----Urspr=FCngliche Nachricht----- Von: De Smet Ringo [mailto:Ringo.De.Smet@staff.telenet.be] Gesendet: Montag, 30. Juni 2008 15:16 An: users@continuum.apache.org Betreff: RE: trying to delete project: JDO error=20 > -----Original Message----- > javax.jdo.JDODataStoreException: Delete request failed:=20 > DELETE FROM `PROJECT` WHERE `ID` =3D ? NestedThrowables:=20 > com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolat > ionException: Cannot delete or update a parent row: a foreign=20 > key constraint fails (`continuum/BUILDRESULT`, CONSTRAINT=20 > `BUILDRESULT_FK3` FOREIGN KEY (`PROJECT_ID_OID`) REFERENCES=20 > `PROJECT` (`ID`)) >=20 > somebody experienced that too ? >=20 Yes! Was the last build of that project a failing one? I noticed that you can only delete projects in Continuum if the last build was succesfull. Ringo=20 ************************************************************* Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie = bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsr= echten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk ge= bruik van de informatie vervat in dit bericht (waaronder de volledige of ge= deeltelijke reproductie of verspreiding onder elke vorm) door andere person= en dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing= heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht= te verwijderen.=20 This e-mail and any attachment thereto may contain information which is con= fidential and/or protected by intellectual property rights and are intended= for the sole use of the addressees. Any use of the information contained h= erein (including but not limited to total or partial reproduction or distri= bution in any form) by other persons than the addressees is prohibited. If = you have received this e-mail in error, please notify the sender and delete= its contents. Ce courriel et les annexes =E9ventuelles peuvent contenir des informations = confidentielles et/ou prot=E9g=E9es par des droits de propri=E9t=E9 intelle= ctuelle. Ce message est adress=E9 exclusivement =E0 son (ses) destinataire(= s). Toute utilisation du contenu de ce message (y compris la reproduction o= u diffusion partielle ou compl=E8te sous toute forme) par une autre personn= e que le(s) destinataire(s) est formellement interdite. Si vous avez re=E7u= ce message par erreur, veuillez pr=E9venir l'exp=E9diteur du message et en= d=E9truire le contenu. ************************************************************* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This email with attachments is solely for the use of the individual or entity to whom it is addressed. Please also be aware that the DnB NOR Group cannot accept any payment orders or other legally binding correspondence wi= th customers as a part of an email.=20 This email message has been virus checked by the anti virus programs used in the DnB NOR Group. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *