svn commit: r1804499 - in /velocity/site/production/engine: 2.0/upgrading.html devel/upgrading.html

[cbrisson]

Author: cbrisson
Date: Wed Aug  9 09:32:00 2017
New Revision: 1804499

URL: http://svn.apache.org/viewvc?rev=1804499&view=rev
Log:
[engine] Add a note about the maven repository path change (production)

Modified:
    velocity/site/production/engine/2.0/upgrading.html
    velocity/site/production/engine/devel/upgrading.html

Modified: velocity/site/production/engine/2.0/upgrading.html
URL: 
http://svn.apache.org/viewvc/velocity/site/production/engine/2.0/upgrading.html?rev=1804499&r1=1804498&r2=1804499&view=diff
==============================================================================
--- velocity/site/production/engine/2.0/upgrading.html (original)
+++ velocity/site/production/engine/2.0/upgrading.html Wed Aug  9 09:32:00 2017
@@ -226,6 +226,14 @@ 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, 2.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>
 <h2 id="upgrading-from-velocity-17x-to-velocity-20x">Upgrading from Velocity 
1.7.x to Velocity 2.0.x<a class="headerlink" 
href="#upgrading-from-velocity-17x-to-velocity-20x" title="Permanent 
link">&para;</a></h2>
+<div class="note">
+Please note that the maven repository path has changed:
+<ul>
+  <li>former path: <code>org/apache/velocity/velocity/1.7.<i>x</i></code></li>
+  <li>new path: 
<code>org/apache/velocity/velocity-engine-core/2.0[.<i>x</i>]</code></li>
+</ul>
+</div>
+
 <p>For busy people: To maximize backward compatibility with Velocity 1.x, be 
sure to include the following lines in your Velocity configuration:</p>
 <div class="codehilite"><pre>runtime.conversion.handler = none
 space.gobbling = bc

Modified: velocity/site/production/engine/devel/upgrading.html
URL: 
http://svn.apache.org/viewvc/velocity/site/production/engine/devel/upgrading.html?rev=1804499&r1=1804498&r2=1804499&view=diff
==============================================================================
--- velocity/site/production/engine/devel/upgrading.html (original)
+++ velocity/site/production/engine/devel/upgrading.html Wed Aug  9 09:32:00 
2017
@@ -226,6 +226,14 @@ 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, 2.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>
 <h2 id="upgrading-from-velocity-17x-to-velocity-20x">Upgrading from Velocity 
1.7.x to Velocity 2.0.x<a class="headerlink" 
href="#upgrading-from-velocity-17x-to-velocity-20x" title="Permanent 
link">&para;</a></h2>
+<div class="note">
+Please note that the maven repository path has changed:
+<ul>
+  <li>former path: <code>org/apache/velocity/velocity/1.7.<i>x</i></code></li>
+  <li>new path: 
<code>org/apache/velocity/velocity-engine-core/2.0[.<i>x</i>]</code></li>
+</ul>
+</div>
+
 <p>For busy people: To maximize backward compatibility with Velocity 1.x, be 
sure to include the following lines in your Velocity configuration:</p>
 <div class="codehilite"><pre>runtime.conversion.handler = none
 space.gobbling = bc