[ https://issues.apache.org/jira/browse/VELOCITY-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bubna resolved VELOCITY-499. ----------------------------------- Resolution: Fixed > Default Velocity LogChute implementations blabber too much > ---------------------------------------------------------- > > Key: VELOCITY-499 > URL: https://issues.apache.org/jira/browse/VELOCITY-499 > Project: Velocity > Issue Type: Bug > Components: Engine > Affects Versions: 1.5 beta1, 1.5 beta2 > Reporter: Henning Schmiedehausen > Assigned To: Nathan Bubna > Priority: Minor > Fix For: 1.6 > > > While debugging engine code, I noticed that at least the AvalonLogChute > (which is the default one if the logkit jar is present which it obviously is > in an engine build) logs at [debug] level if there is no explicit > configuration present. That is IMHO bad because it swamps an unsuspecting > user with a lot of detail that is not needed. > I propose that we make sure that AvalonLogChute, JdkLogChute, Log4JLogChute > and SystemLogChute log only WARN and ERROR level if no configuration is > present (default configuration). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]