velocity-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cbris...@apache.org
Subject svn commit: r1752608 - in /velocity/site: cms/trunk/content/engine/1.7/ cms/trunk/content/engine/devel/ production/engine/1.7/ production/engine/devel/
Date Thu, 14 Jul 2016 09:33:12 GMT
Author: cbrisson
Date: Thu Jul 14 09:33:12 2016
New Revision: 1752608

URL: http://svn.apache.org/viewvc?rev=1752608&view=rev
Log:
[site] fix wrong anchor

Modified:
    velocity/site/cms/trunk/content/engine/1.7/developer-guide.mdtext
    velocity/site/cms/trunk/content/engine/devel/developer-guide.mdtext
    velocity/site/cms/trunk/content/engine/devel/upgrading.mdtext
    velocity/site/production/engine/1.7/developer-guide.html
    velocity/site/production/engine/devel/changes.html
    velocity/site/production/engine/devel/developer-guide.html
    velocity/site/production/engine/devel/upgrading.html

Modified: velocity/site/cms/trunk/content/engine/1.7/developer-guide.mdtext
URL: http://svn.apache.org/viewvc/velocity/site/cms/trunk/content/engine/1.7/developer-guide.mdtext?rev=1752608&r1=1752607&r2=1752608&view=diff
==============================================================================
--- velocity/site/cms/trunk/content/engine/1.7/developer-guide.mdtext (original)
+++ velocity/site/cms/trunk/content/engine/1.7/developer-guide.mdtext Thu Jul 14 09:33:12
2016
@@ -862,7 +862,7 @@ To illustrate, here is an example taken
 
 `runtime.references.strict = false`
 
-> New in Velocity 1.6, when set to true Velocity will throw a `MethodInvocationException`
for references that are not defined in the context, or have not been defined with a #set directive.
 This setting will also throw an exception if an attempt is made to call a non-existing property
on an object or if the object is null.  When this property is true then property 'directive.set.null.allowed'
is also set to true. Also, 'directive.foreach.skip.invalid' defaults to true when this property
is true, but explicitly setting 'directive.foreach.skip.invalid' will override this default.
For a complete discussion see <a href="user-guide.html#strictreferences">Strict References
Setting</a>.
+> New in Velocity 1.6, when set to true Velocity will throw a `MethodInvocationException`
for references that are not defined in the context, or have not been defined with a #set directive.
 This setting will also throw an exception if an attempt is made to call a non-existing property
on an object or if the object is null.  When this property is true then property 'directive.set.null.allowed'
is also set to true. Also, 'directive.foreach.skip.invalid' defaults to true when this property
is true, but explicitly setting 'directive.foreach.skip.invalid' will override this default.
For a complete discussion see <a href="user-guide.html#strict-reference-mode">Strict
References Setting</a>.
 > 
 > `runtime.references.strict.escape = false` Changes escape behavior such that putting
a forward slash before a reference or macro always escapes the reference or macro and absorbs
the forward slash regardless if the reference or macro is defined. For example "\$foo" always
renders as "$foo", or "\#foo()" is always rendered as "#foo()".  This escape behavior is of
use in strict mode since unintended strings of characters that look like references or macros
will throw an exception.  This provides an easy way to escape these references.  However,
even in non-strict mode the developer may find this a more consistent and reliable method
for escaping.
 

Modified: velocity/site/cms/trunk/content/engine/devel/developer-guide.mdtext
URL: http://svn.apache.org/viewvc/velocity/site/cms/trunk/content/engine/devel/developer-guide.mdtext?rev=1752608&r1=1752607&r2=1752608&view=diff
==============================================================================
--- velocity/site/cms/trunk/content/engine/devel/developer-guide.mdtext (original)
+++ velocity/site/cms/trunk/content/engine/devel/developer-guide.mdtext Thu Jul 14 09:33:12
2016
@@ -865,7 +865,7 @@ To illustrate, here is an example taken
 
 `runtime.references.strict = false`
 
-> New in Velocity 1.6, when set to true Velocity will throw a `MethodInvocationException`
for references that are not defined in the context, or have not been defined with a #set directive.
 This setting will also throw an exception if an attempt is made to call a non-existing property
on an object or if the object is null.  When this property is true then property 'directive.set.null.allowed'
is also set to true. Also, 'directive.foreach.skip.invalid' defaults to true when this property
is true, but explicitly setting 'directive.foreach.skip.invalid' will override this default.
For a complete discussion see <a href="user-guide.html#strictreferences">Strict References
Setting</a>.
+> New in Velocity 1.6, when set to true Velocity will throw a `MethodInvocationException`
for references that are not defined in the context, or have not been defined with a #set directive.
 This setting will also throw an exception if an attempt is made to call a non-existing property
on an object or if the object is null.  When this property is true then property 'directive.set.null.allowed'
is also set to true. Also, 'directive.foreach.skip.invalid' defaults to true when this property
is true, but explicitly setting 'directive.foreach.skip.invalid' will override this default.
For a complete discussion see <a href="user-guide.html#strict-reference-mode">Strict
References Setting</a>.
 > 
 > `runtime.references.strict.escape = false` Changes escape behavior such that putting
a forward slash before a reference or macro always escapes the reference or macro and absorbs
the forward slash regardless if the reference or macro is defined. For example "\$foo" always
renders as "$foo", or "\#foo()" is always rendered as "#foo()".  This escape behavior is of
use in strict mode since unintended strings of characters that look like references or macros
will throw an exception.  This provides an easy way to escape these references.  However,
even in non-strict mode the developer may find this a more consistent and reliable method
for escaping.
 

Modified: velocity/site/cms/trunk/content/engine/devel/upgrading.mdtext
URL: http://svn.apache.org/viewvc/velocity/site/cms/trunk/content/engine/devel/upgrading.mdtext?rev=1752608&r1=1752607&r2=1752608&view=diff
==============================================================================
--- velocity/site/cms/trunk/content/engine/devel/upgrading.mdtext (original)
+++ velocity/site/cms/trunk/content/engine/devel/upgrading.mdtext Thu Jul 14 09:33:12 2016
@@ -6,6 +6,10 @@ Release with the same major number (1.x)
 
 ### Upgrading from Velocity 1.7
 
+API changes:
+
++ the internal Context API now enforces String keys, this may break custom Context implementations
at compile-time.
+
 VTL Syntax changes:
 
 + the hypen ( `-` ) cannot be used in variable names anymore

Modified: velocity/site/production/engine/1.7/developer-guide.html
URL: http://svn.apache.org/viewvc/velocity/site/production/engine/1.7/developer-guide.html?rev=1752608&r1=1752607&r2=1752608&view=diff
==============================================================================
--- velocity/site/production/engine/1.7/developer-guide.html (original)
+++ velocity/site/production/engine/1.7/developer-guide.html Thu Jul 14 09:33:12 2016
@@ -1095,7 +1095,7 @@ file.resource.loader.modificationCheckIn
 <h3 id="strict-reference-setting">Strict Reference Setting<a class="headerlink"
href="#strict-reference-setting" title="Permanent link">&para;</a></h3>
 <p><code>runtime.references.strict = false</code></p>
 <blockquote>
-<p>New in Velocity 1.6, when set to true Velocity will throw a <code>MethodInvocationException</code>
for references that are not defined in the context, or have not been defined with a #set directive.
 This setting will also throw an exception if an attempt is made to call a non-existing property
on an object or if the object is null.  When this property is true then property 'directive.set.null.allowed'
is also set to true. Also, 'directive.foreach.skip.invalid' defaults to true when this property
is true, but explicitly setting 'directive.foreach.skip.invalid' will override this default.
For a complete discussion see <a href="user-guide.html#strictreferences">Strict References
Setting</a>.</p>
+<p>New in Velocity 1.6, when set to true Velocity will throw a <code>MethodInvocationException</code>
for references that are not defined in the context, or have not been defined with a #set directive.
 This setting will also throw an exception if an attempt is made to call a non-existing property
on an object or if the object is null.  When this property is true then property 'directive.set.null.allowed'
is also set to true. Also, 'directive.foreach.skip.invalid' defaults to true when this property
is true, but explicitly setting 'directive.foreach.skip.invalid' will override this default.
For a complete discussion see <a href="user-guide.html#strict-reference-mode">Strict
References Setting</a>.</p>
 <p><code>runtime.references.strict.escape = false</code> Changes escape
behavior such that putting a forward slash before a reference or macro always escapes the
reference or macro and absorbs the forward slash regardless if the reference or macro is defined.
For example "\$foo" always renders as "$foo", or "#foo()" is always rendered as "#foo()".
 This escape behavior is of use in strict mode since unintended strings of characters that
look like references or macros will throw an exception.  This provides an easy way to escape
these references.  However, even in non-strict mode the developer may find this a more consistent
and reliable method for escaping.</p>
 </blockquote>
 <h3 id="string-interpolation">String Interpolation<a class="headerlink" href="#string-interpolation"
title="Permanent link">&para;</a></h3>

Modified: velocity/site/production/engine/devel/changes.html
URL: http://svn.apache.org/viewvc/velocity/site/production/engine/devel/changes.html?rev=1752608&r1=1752607&r2=1752608&view=diff
==============================================================================
--- velocity/site/production/engine/devel/changes.html (original)
+++ velocity/site/production/engine/devel/changes.html Thu Jul 14 09:33:12 2016
@@ -316,6 +316,13 @@ h2:hover > .headerlink, h3:hover > .head
         <td>
           <img src="images/fix.png"/>
         </td>
+        <td> InvalidReferenceHandler events should not be triggered by null values,
or by references testing inside #if / #elseif. Thanks to Renato Steiner for his testcase.
. Fixes <a href="https://issues.apache.org/jira/browse/VELOCITY-553">VELOCITY-553</a>.
</td>
+        <td>cbrisson</td>
+      </tr>
+      <tr>
+        <td>
+          <img src="images/fix.png"/>
+        </td>
         <td> Take advantage of the major version jump to enforce String keys in internal
Context API . Fixes <a href="https://issues.apache.org/jira/browse/VELOCITY-266">VELOCITY-266</a>.
</td>
         <td>cbrisson</td>
       </tr>

Modified: velocity/site/production/engine/devel/developer-guide.html
URL: http://svn.apache.org/viewvc/velocity/site/production/engine/devel/developer-guide.html?rev=1752608&r1=1752607&r2=1752608&view=diff
==============================================================================
--- velocity/site/production/engine/devel/developer-guide.html (original)
+++ velocity/site/production/engine/devel/developer-guide.html Thu Jul 14 09:33:12 2016
@@ -1094,7 +1094,7 @@ file.resource.loader.modificationCheckIn
 <h3 id="strict-reference-setting">Strict Reference Setting<a class="headerlink"
href="#strict-reference-setting" title="Permanent link">&para;</a></h3>
 <p><code>runtime.references.strict = false</code></p>
 <blockquote>
-<p>New in Velocity 1.6, when set to true Velocity will throw a <code>MethodInvocationException</code>
for references that are not defined in the context, or have not been defined with a #set directive.
 This setting will also throw an exception if an attempt is made to call a non-existing property
on an object or if the object is null.  When this property is true then property 'directive.set.null.allowed'
is also set to true. Also, 'directive.foreach.skip.invalid' defaults to true when this property
is true, but explicitly setting 'directive.foreach.skip.invalid' will override this default.
For a complete discussion see <a href="user-guide.html#strictreferences">Strict References
Setting</a>.</p>
+<p>New in Velocity 1.6, when set to true Velocity will throw a <code>MethodInvocationException</code>
for references that are not defined in the context, or have not been defined with a #set directive.
 This setting will also throw an exception if an attempt is made to call a non-existing property
on an object or if the object is null.  When this property is true then property 'directive.set.null.allowed'
is also set to true. Also, 'directive.foreach.skip.invalid' defaults to true when this property
is true, but explicitly setting 'directive.foreach.skip.invalid' will override this default.
For a complete discussion see <a href="user-guide.html#strict-reference-mode">Strict
References Setting</a>.</p>
 <p><code>runtime.references.strict.escape = false</code> Changes escape
behavior such that putting a forward slash before a reference or macro always escapes the
reference or macro and absorbs the forward slash regardless if the reference or macro is defined.
For example "\$foo" always renders as "$foo", or "#foo()" is always rendered as "#foo()".
 This escape behavior is of use in strict mode since unintended strings of characters that
look like references or macros will throw an exception.  This provides an easy way to escape
these references.  However, even in non-strict mode the developer may find this a more consistent
and reliable method for escaping.</p>
 </blockquote>
 <h3 id="string-interpolation">String Interpolation<a class="headerlink" href="#string-interpolation"
title="Permanent link">&para;</a></h3>

Modified: velocity/site/production/engine/devel/upgrading.html
URL: http://svn.apache.org/viewvc/velocity/site/production/engine/devel/upgrading.html?rev=1752608&r1=1752607&r2=1752608&view=diff
==============================================================================
--- velocity/site/production/engine/devel/upgrading.html (original)
+++ velocity/site/production/engine/devel/upgrading.html Thu Jul 14 09:33:12 2016
@@ -225,6 +225,10 @@ h2:hover > .headerlink, h3:hover > .head
 <h2 id="upgrading-from-earlier-versions">Upgrading from earlier versions<a class="headerlink"
href="#upgrading-from-earlier-versions" title="Permanent link">&para;</a></h2>
 <p>Release with the same major number (1.x) are intended to be drop-in replacements.
However, in most cases the versions of dependency jars must be adjusted because newer versions
of Velocity might require updates.</p>
 <h3 id="upgrading-from-velocity-17">Upgrading from Velocity 1.7<a class="headerlink"
href="#upgrading-from-velocity-17" title="Permanent link">&para;</a></h3>
+<p>API changes:</p>
+<ul>
+<li>the internal Context API now enforces String keys, this may break custom Context
implementations at compile-time.</li>
+</ul>
 <p>VTL Syntax changes:</p>
 <ul>
 <li>the hypen ( <code>-</code> ) cannot be used in variable names anymore</li>



Mime
View raw message