Author: cbrisson
Date: Sun May 5 14:00:09 2019
New Revision: 1858688
URL: http://svn.apache.org/viewvc?rev=1858688&view=rev
Log:
[site/engine] Document runtime.log.track_location
Modified:
velocity/site/cms/trunk/content/engine/devel/configuration.mdtext
Modified: velocity/site/cms/trunk/content/engine/devel/configuration.mdtext
URL:
http://svn.apache.org/viewvc/velocity/site/cms/trunk/content/engine/devel/configuration.mdtext?rev=1858688&r1=1858687&r2=1858688&view=diff
==============================================================================
--- velocity/site/cms/trunk/content/engine/devel/configuration.mdtext (original)
+++ velocity/site/cms/trunk/content/engine/devel/configuration.mdtext Sun May
5 14:00:09 2019
@@ -68,6 +68,7 @@ The following tree gathers all non depre
| +-- log_invalid_method_calls = true
| +-- log_invalid_references = true
| +-- name = org.apache.velocity
+ | +-- track_location = false
+-- strict_math = false
+-- strict_mode. +-- enable = false
| +-- escape = false
@@ -100,6 +101,10 @@ The following tree gathers all non depre
> Property to turn off the log output when a method call isn't valid or has
> thrown. Good thing to turn off in production, but very valuable for
> debugging.
+**`runtime.log.track_location = false`**
+
+> (Since 2.2). When set to true, Velocity will populate [slf4j
MDC](https://logback.qos.ch/manual/mdc.html) with the `file`, `line` and
`context` tags during the template rendering process. When using an MDC-aware
slf4j backend, you can display template locations in logs. Be aware that it can
have a small performance impact.
+
## VTL Directives
### #define() Directive
