You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Byron Foster (JIRA)" <de...@velocity.apache.org> on 2008/10/10 05:44:47 UTC
[jira] Updated: (VELOCITY-624) LogChute's only set log level if
specified
[ https://issues.apache.org/jira/browse/VELOCITY-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Byron Foster updated VELOCITY-624:
----------------------------------
Attachment: LogChuteNoForce.patch
> LogChute's only set log level if specified
> ------------------------------------------
>
> Key: VELOCITY-624
> URL: https://issues.apache.org/jira/browse/VELOCITY-624
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.6
> Reporter: Byron Foster
> Attachments: LogChuteNoForce.patch
>
>
> The patch changes the behavior of Log4JLogChute and JdkLogChute such that the log level is only set if the coresponding runtime property is set. for example 'runtime.log.logsystem.log4j.logger.level'. Beforet this change, log level was set to 'WARN' if the level wasn't set with a property, which would override logger config file settings if the logger was configured before initializing velocity.
--
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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org