[jboss-dev] Embedded Jopr snapshot included in the build!

[Dimitris Andreadis]

David M. Lloyd wrote:
> On 04/15/2009 05:48 AM, Jaikiran Pai wrote:
>> Looks good :)
>>
>> On a related note, I guess we could do something about the INFO level 
>> logs that flood the console when the admin-console is being deployed 
>> and accessed? Looking at what is being logged, it doesn't look like 
>> they should be logged at INFO level:
> 
> The rules are:

+1

Another way to think about it:

> - One-time, terse messages can be at INFO
Goes to console - mostly interesting to users/admins

> - Per-deployment/lifecycle stuff can be no higher than DEBUG
Might go to server.log - mostly interesting to developers & support

> - Per-request stuff can be no higher than TRACE
always use isTraceEnabled() - for low level troubleshooting

So why every developer wants to monopolize console output?

a) because we like seeing "our" stuff doing something
b) because we are lazy changing logging options when developing subsystems.

Also, one exception for per-deployment logging:

INFO - deployed path/to/xyz.jar
INFO - undeployed path/to/xyz.jar

> 
> AFAICT, Seam is not "above the law" here.  So why are we talking about 
> yet more exceptions in the logging config?  How about the SEAM guys fix 
> the problem?
> 
> I hope you guys are aware that we have a reputation for having absurdly 
> spammy log files - especially Seam apps.
> 
> - DML
>