From costin@eng.sun.com Thu Apr 6 15:05:45 2000 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 31247 invoked from network); 6 Apr 2000 15:05:45 -0000 Received: from adsl-63-198-47-229.dsl.snfc21.pacbell.net (HELO costin.dnt.ro) (63.198.47.229) by locus.apache.org with SMTP; 6 Apr 2000 15:05:45 -0000 Received: from eng.sun.com (simona.dnt.ro [192.168.4.2]) by costin.dnt.ro (8.9.3+Sun/8.9.1) with ESMTP id IAA13869 for ; Thu, 6 Apr 2000 08:05:26 -0700 (PDT) Message-ID: <38ECA83D.7D480D4D@eng.sun.com> Date: Thu, 06 Apr 2000 08:07:41 -0700 From: Costin Manolache X-Mailer: Mozilla 4.72 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: tomcat-dev@jakarta.apache.org Subject: Re: possible Tomcat 3.1 issues References: <852568B9.004390C8.00@d54mta04.raleigh.ibm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Regarding XML output - I can remove the -like formating for all "normal" message today. For debug messages - most people will never see them, so I would let them in - with hope that in next release we'll be able to implement a better solution. It seems the problem is not if we want xml or not ( most people agree there are advantages in using an easy-to-parse format), but in how it is implemented, and the fact that we don't generate plain text too. Please, let's mark the workspace and create the 3.1 RC this week - it seems only few people are working on bugs, and we stoped all development for too long ( almost 3 weeks ). This is not the last tomcat - we'll have 3.2, 3.3, etc ( I hope ) - the release cycle is far too long for an open source project. Costin