+/-0 : The database pool creation portlet doesn't work for the Embedded Derby driver in Tomcat. It doesn't log an error either, just bails midway through. I'm not sure what's going on -- the same procedure worked fine in Jetty, and a third-party database like PostgreSQL doesn't have that same problem. I wonder if our Jetty config includes some Derby dependencies that the Tomcat config doesn't? I'll poke around a bit. I guess no one's probably willing to hold up the release on account of this... :)
Aaron On 1/3/06, Sachin Patel <[EMAIL PROTECTED]> wrote: > forwarding this on behalf of Matt... > > > - sachin > > > > > Begin forwarded message: > > From: Matt Hogstrom <[EMAIL PROTECTED]> > Date: January 3, 2006 9:47:28 AM EST > To: [EMAIL PROTECTED] > Subject: [Fwd: [Vote] 1.0 Release - Do we ship it?] > > > Can you forward thsi for me? I'm still getting SPAM errors. I've sent a > note to Ken to see if he can help me decipher what's going on. > > -------- Original Message -------- > Subject: [Vote] 1.0 Release - Do we ship it? > Date: Tue, 03 Jan 2006 09:21:30 -0500 > From: Matt Hogstrom <[EMAIL PROTECTED]> > To: [email protected] > > All, > > We have had the last candidate out and available since 12/22. I personally > have > had a chance to put the 12/22 build under performance stress and I'm > satisfied > that the build is stable and runs in a variety of modes using DayTrader. > > Despite the Christmas Holidays I have seen some traffic related to htis > release > on the list so some folks have been kicking it around as well. At this time > I'd > like to call a vote to release 1.0. > > [ ] +1 Release 1.0 > [ ] -1 Do not release 1.0 (Reasons included) > > Looks like we got through the last remaining significant bugs and thansk to > all > who worked up to the end to get this release out there. > > Matt > > > > >
