Author: cbrisson
Date: Mon Nov 7 11:21:43 2016
New Revision: 1768502
URL: http://svn.apache.org/viewvc?rev=1768502&view=rev
Log:
[site] push last change into production
Modified:
velocity/site/production/tools/devel/upgrading.html
Modified: velocity/site/production/tools/devel/upgrading.html
URL:
http://svn.apache.org/viewvc/velocity/site/production/tools/devel/upgrading.html?rev=1768502&r1=1768501&r2=1768502&view=diff
==============================================================================
--- velocity/site/production/tools/devel/upgrading.html (original)
+++ velocity/site/production/tools/devel/upgrading.html Mon Nov 7 11:21:43 2016
@@ -219,7 +219,6 @@ h2:hover > .headerlink, h3:hover > .head
<ul>
<li><a href="#upgrading-velocitytools">Upgrading VelocityTools</a></li>
<li><a href="#upgrading-to-30">Upgrading to 3.0</a></li>
-<li><a href="#upgrading-to-21">Upgrading to 2.1</a></li>
<li><a href="#upgrading-to-20">Upgrading to 2.0</a><ul>
<li><a href="#renamings-in-20">Renamings in 2.0</a></li>
<li><a href="#deprecations-in-20">Deprecations in 2.0</a></li>
@@ -233,9 +232,8 @@ h2:hover > .headerlink, h3:hover > .head
</div>
<h2 id="upgrading-to-30">Upgrading to 3.0<a class="headerlink"
href="#upgrading-to-30" title="Permanent link">¶</a></h2>
<p>Velocity Tools, as well as Velocity Engine 2.0+, has switched to the SLF4J
logging facade. All logger objects are now <code>orf.slf4j.Logger</code>
instances.</p>
-<h2 id="upgrading-to-21">Upgrading to 2.1<a class="headerlink"
href="#upgrading-to-21" title="Permanent link">¶</a></h2>
-<p class="note">TODO
-</p>
+<p>All objects, methods and configuration formats deprecated in 2.0 have been
suppressed.</p>
+<p>For custom objects refering directly to the Velocity Engine API, please
refer to the <a
href="http://velocity.apache.org/engine/2.0/upgrading.html">Velocity Engine 2.0
Upgrading section</a>.</p>
<h2 id="upgrading-to-20">Upgrading to 2.0<a class="headerlink"
href="#upgrading-to-20" title="Permanent link">¶</a></h2>
<p>VelocityTools 2.0 marks the most significant set of upgrades and changes
ever done for the VelocityTools library. In order to provide flexible
configurations, lazy-loading for tools, and a host of other improvements,
almost all of the tool management and configuration code from Tools 1.x has
been deprecated and replaced by completely different APIs. Thankfully, we were
able to continue supporting old toolbox.xml configuration files and old tool
design patterns, though these too have been deprecated and are unable to take
full advantage of many of the new features.</p>
<p>Still, as such things have only been deprecated and not removed,
<strong>the first step in upgrading to 2.0 is simply replacing your old
VelocityTools jar with the 2.0 jar</strong>. If this causes any errors for you,
please report them to [email protected], so that we can fix it and help
you work around it in the meantime.</p>