Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 99666 invoked by uid 500); 26 Jul 2002 16:43:35 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 99655 invoked from network); 26 Jul 2002 16:43:34 -0000 Reply-To: From: "Berin Loritsch" To: Subject: System.out.println() in Main.java Date: Fri, 26 Jul 2002 12:43:19 -0400 Message-ID: <004701c234c3$8c2b24e0$ac00a8c0@Gabriel> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N It has come to my attention that we have a whole mess of System.out.println(...) messages in org.apache.cocoon.Main.java. I find this very annoying. I propose converting all of those into INFO level log messages for the category "cocoon.cli". We can then use the logkit.xconf file to determine exactly where those messages should go. IMO they clutter the output of an ANT task. "They that give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org