Author: hboutemy
Date: Sat Apr 9 05:53:22 2016
New Revision: 1738323
URL: http://svn.apache.org/viewvc?rev=1738323&view=rev
Log:
fixed content breaking Velocity execution that was introduced in r1732238
Modified:
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/creating-content.apt.vm
Modified:
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/creating-content.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/creating-content.apt.vm?rev=1738323&r1=1738322&r2=1738323&view=diff
==============================================================================
---
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/creating-content.apt.vm
(original)
+++
maven/plugins/trunk/maven-site-plugin/src/site/apt/examples/creating-content.apt.vm
Sat Apr 9 05:53:22 2016
@@ -168,8 +168,8 @@ Creating Content
<<Note:>> {{{http://velocity.apache.org/}Apache Velocity}} is used to apply
the
filtering. Because Velocity uses a dot-notation to traverse beans you
<<cannot>>
use dotted properties defined in <<<\<properties\>>>> directly. It is
generally
- advised to access properties by using the <<<$context>>> tool.
- E.g., with <<<$context.get("my.property")>>>.
+ advised to access properties by using the <<<${esc.d}context>>> tool.
+ E.g., with <<<${esc.d}context.get("my.property")>>>.
Some properties are defined by default: see
{{{/doxia/doxia-sitetools/doxia-site-renderer/#Velocity_processing} Doxia
Site Renderer's Velocity processing reference}}
