cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <>
Subject Re: [Cocoon CLI] logging with Treeprocessor too verbose
Date Tue, 09 Jul 2002 16:07:03 GMT

Sylvain Wallez wrote:
> Nicola Ken Barozzi wrote:
>> 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?
> Remember our discussion on log levels : debug is for debugging the class 
> (i.e. targeted at developpers) while info is to know what the class does.


> In the case of the sitemap engine, logging an info message when a 
> matcher matches helps the user to know the path taken in the sitemap to 
> process a request.
> IMO, this kind of info isn't needed in CLI, so I would raise the default 
> CLI log level to warn.

Warn gives no clue to the user of what is happening...

I'm asking you for a suggestion, since in the loglevel there is no 
user-info level, and maybe it's not to be given to the logger anyway... 
or just make another logging cat for the user and use that.

How can we do iut with CLI?

>> Also, each broken link shows a stacktrace, which really sucks. 
> It's broken links that suck ;)


>> Is it ok if we remove it? 
> What do you want to remove ? The stacktrace or the whole message when a 
> broken link is encoutered ?
> I'm -1 for removing the whole message : it's bad to ignore broken links. 
> If you don't see them, you may deploy broken pages on a live site.

Sure, it's the stacktrace I'm talking about.

Nicola Ken Barozzi         
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)

To unsubscribe, e-mail:
For additional commands, email:

View raw message