Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 63438 invoked from network); 2 Mar 2001 23:21:14 -0000 Received: from e21.nc.us.ibm.com (32.97.136.227) by h31.sny.collab.net with SMTP; 2 Mar 2001 23:21:14 -0000 Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [9.37.3.209]) by e21.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id SAA61800 for ; Fri, 2 Mar 2001 18:16:40 -0600 Received: from d04nm301.raleigh.ibm.com (d04nm301.raleigh.ibm.com [9.67.228.166]) by southrelay02.raleigh.ibm.com (8.11.2/NCO v4.95) with ESMTP id f22NLEp98856 for ; Fri, 2 Mar 2001 18:21:14 -0500 Importance: Normal Subject: Re: [GUMP] Build Failure - Cocoon2 To: cocoon-dev@xml.apache.org X-Mailer: Lotus Notes Release 5.0.4 June 8, 2000 Message-ID: From: "Sam Ruby" Date: Fri, 2 Mar 2001 18:20:51 -0500 X-MIMETrack: Serialize by Router on D04NM301/04/M/IBM(Release 5.0.6 |December 14, 2000) at 03/02/2001 06:21:16 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Stefano Mazzocchi wrote: > > I'll give a good look at the code tonight, maybe I have a > few brain cycles to throw in. If you have a few cycles, take a look at the Cocoon1 failure. I'm not particular how it gets fixed - update to the latest Turbine interfaces, backport the DB connection pool used by Cocoon2, whatever. Once it builds clean, I can automatically forward on failure notification of this project too. http://jakarta.apache.org/builds/gump/2001-03-02/xml-cocoon.html - Sam Ruby