Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 25947 invoked from network); 12 Nov 1999 00:30:14 -0000 Received: from prv-mail20.provo.novell.com (137.65.82.195) by apache.org with SMTP; 12 Nov 1999 00:30:14 -0000 Received: from INET-PRV-Message_Server by prv-mail20.provo.novell.com with Novell_GroupWise; Thu, 11 Nov 1999 17:29:25 -0700 Message-Id: X-Mailer: Novell GroupWise Internet Agent 5.5.2.1 Date: Thu, 11 Nov 1999 17:29:24 -0700 From: "Danno Ferrin" To: , Subject: Re: Bug in Taglibs Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Really? I am working off of the code from jakarta-tomcat_19991111000507_ta= r.gz, which was a build from yeterday. However I notice that since a = little while ago the tomcat tarball includes tools and watchdog, and a = *second* jakarta-tomcat directory. I am building using build at the first = jakarta-tomcat level. Should I be doing the second level build to get the = fixed code? It is quite confusing to have two separate sourceses in the = tarball. >>> Anil.Vijendran@eng.sun.com 11/11/99 05:13PM >>> Hi Danno, Yep, I know about this bug. It was fixed atleast a few weeks back. If you = are using the latest sources, you shouldn't be seeing this. Danno Ferrin wrote: > An interesting compiler/verfier bug of 1.1 and 1.2 causes a legit taglib = definition to fail on a verification error. Basically jasper creates a = code block > try { > do { > // end > // begin > } while (false); > } catch (Throwable t) { > System.err.println("Caught: "); > t.printStackTrace(); > } finally { > }