Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 78275 invoked by uid 500); 9 Jul 2002 15:28:22 -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 78257 invoked from network); 9 Jul 2002 15:28:21 -0000 Message-ID: <3D2B00FA.9010308@apache.org> Date: Tue, 09 Jul 2002 17:27:54 +0200 From: Nicola Ken Barozzi Reply-To: nicolaken@apache.org Organization: Apache Software Foundation User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: [Cocoon CLI] logging with Treeprocessor too verbose References: <3D2AFCF0.1080601@ieee.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Before treeprocessor, the CLI just said what it was traversing and made good output for the user. Now on level -INFO there are so many messages that I have to turn it off completely. Should we revert the behaviour? Also, each broken link shows a stacktrace, which really sucks. Is it ok if we remove it? -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org