You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Claude Brisson (JIRA)" <ji...@apache.org> on 2019/05/05 13:55:00 UTC
[jira] [Resolved] (VELOCITY-916) Track template location in logs
using slf4j MDC mechanism
[ https://issues.apache.org/jira/browse/VELOCITY-916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claude Brisson resolved VELOCITY-916.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.2
Implemented by commit 1858687.
Since this feature can have a performance impact, it is disabled by default. One can enable it, typically in a development environment, using the new configuration key:
{{runtime.log.track_location = true}}
> Track template location in logs using slf4j MDC mechanism
> ---------------------------------------------------------
>
> Key: VELOCITY-916
> URL: https://issues.apache.org/jira/browse/VELOCITY-916
> Project: Velocity
> Issue Type: New Feature
> Components: Engine
> Affects Versions: 2.2
> Reporter: Claude Brisson
> Assignee: Claude Brisson
> Priority: Major
> Fix For: 2.2
>
>
> Slf4j MDC (Mapped Diagnostic Context) allows to set contextual key/value pairs, which can be used in MDC-aware logger implementations.
> The proposed feature is to populate "file", "line" and "column" MDC tags during template rendering.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org