Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 8916 invoked from network); 9 May 2003 12:42:06 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 9 May 2003 12:42:06 -0000 Received: (qmail 26101 invoked by uid 97); 9 May 2003 12:44:09 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@nagoya.betaversion.org Received: (qmail 26094 invoked from network); 9 May 2003 12:44:09 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 9 May 2003 12:44:09 -0000 Received: (qmail 8097 invoked by uid 500); 9 May 2003 12:41:57 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 8071 invoked from network); 9 May 2003 12:41:56 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 9 May 2003 12:41:56 -0000 Received: (qmail 26087 invoked by uid 50); 9 May 2003 12:44:00 -0000 Date: 9 May 2003 12:44:00 -0000 Message-ID: <20030509124400.26086.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 19789] - javac errors display above custom error page for compile-time exceptions in 4.1.21 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19789 javac errors display above custom error page for compile-time exceptions in 4.1.21 ------- Additional Comments From remm@apache.org 2003-05-09 12:44 ------- I attempted to reproduce the problem according to the information you provided, and could not. In a bug report, you have to point out *precisely* at a specific flaw, especially when the report is hinting at a very noticeable flaw in a build that has recieved wide testing and usage since its release. We cannot be creative and imaginative when dealing with bug reports. Also, you should make sure that what you post is accurate. This is clearly not the case in your reply. Please don't reopen the bug unless you can provide a ready to use test case. --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org