Author: cbrisson
Date: Mon Oct 1 10:26:56 2018
New Revision: 1842464
URL: http://svn.apache.org/viewvc?rev=1842464&view=rev
Log:
[site] Push previous tools change (plus how-we-are page) to production
Modified:
velocity/site/production/tools/devel/changes.html
velocity/site/production/tools/devel/dependencies.html
velocity/site/production/tools/devel/frameworks.html
velocity/site/production/tools/devel/generic.html
velocity/site/production/tools/devel/index.html
velocity/site/production/tools/devel/upgrading.html
velocity/site/production/tools/devel/view.html
velocity/site/production/who-we-are.html
Modified: velocity/site/production/tools/devel/changes.html
URL:
http://svn.apache.org/viewvc/velocity/site/production/tools/devel/changes.html?rev=1842464&r1=1842463&r2=1842464&view=diff
==============================================================================
--- velocity/site/production/tools/devel/changes.html (original)
+++ velocity/site/production/tools/devel/changes.html Mon Oct 1 10:26:56 2018
@@ -280,6 +280,55 @@ h2:hover > .headerlink, h3:hover > .head
<tbody>
<tr>
<td>
+ <img src="images/add.png"/>
+ </td>
+ <td> upgraded to servlet API 3.1.0 . </td>
+ <td>michaelo</td>
+ </tr>
+ <tr>
+ <td>
+ <img src="images/fix.png"/>
+ </td>
+ <td> JsonTool now uses an explicit dependency to <code>
com.github.cliftonlabs.json-simple </code> . </td>
+ <td>michaelo</td>
+ </tr>
+ <tr>
+ <td>
+ <img src="images/fix.png"/>
+ </td>
+ <td> The <code> tools.xml </code> file can now use XInclude file
inclusion mechanism . </td>
+ <td>cbrisson</td>
+ </tr>
+ <tr>
+ <td>
+ <img src="images/fix.png"/>
+ </td>
+ <td> Most tools are now serializable . </td>
+ <td>cbrisson</td>
+ </tr>
+ <tr>
+ <td>
+ <img src="images/fix.png"/>
+ </td>
+ <td> CollectionTool.sort() now filters out null elements . </td>
+ <td>cbrisson</td>
+ </tr>
+ <tr>
+ <td>
+ <img src="images/fix.png"/>
+ </td>
+ <td> ViewLayoutServlet layout cannot be changed using GET parameters,
unless configured with the <code> tools.view.servlet.layout.dynamic </code>
servlet param to true . </td>
+ <td>cbrisson</td>
+ </tr>
+ <tr>
+ <td>
+ <img src="images/fix.png"/>
+ </td>
+ <td> Review tools-view initialization: default tools are now loaded
only when asked for via the <code> org.apache.velocity.tools.loadDefaults
</code> parameter (as an init or servlet parameter). . </td>
+ <td>cbrisson</td>
+ </tr>
+ <tr>
+ <td>
<img src="images/fix.png"/>
</td>
<td> Drop undocumented autoloaded tools feature, and have
org.apache.velocity.tools.loadDefaults default to false . </td>
@@ -412,13 +461,6 @@ h2:hover > .headerlink, h3:hover > .head
<td>cbrisson</td>
</tr>
<tr>
- <td>
- <img src="images/add.png"/>
- </td>
- <td> upgraded to servlet API 3.0.1 . </td>
- <td>cbrisson</td>
- </tr>
- <tr>
<td>
<img src="images/fix.png"/>
</td>
Modified: velocity/site/production/tools/devel/dependencies.html
URL:
http://svn.apache.org/viewvc/velocity/site/production/tools/devel/dependencies.html?rev=1842464&r1=1842463&r2=1842464&view=diff
==============================================================================
--- velocity/site/production/tools/devel/dependencies.html (original)
+++ velocity/site/production/tools/devel/dependencies.html Mon Oct 1 10:26:56
2018
@@ -251,12 +251,12 @@ h2:hover > .headerlink, h3:hover > .head
<td>Required for <a href="config-xml.html">xml configuration</a> (and <a
href="apidocs/org/apache/velocity/tools/view/UiDependencyTool.html">UIDependencyTool</a>
view tool)</td>
</tr>
<tr>
-<td>com.googlecode.json-simple</td>
+<td>com.github.cliftonlabs.json-simple</td>
<td>1.1.1</td>
<td>Yes</td>
<td>No</td>
<td>No</td>
-<td>Required only at compilation time for <a
href="apidocs/org/apache/velocity/tools/generic/JsonTool.html">JsonTool</a></td>
+<td>Required for <a
href="apidocs/org/apache/velocity/tools/generic/JsonTool.html">JsonTool</a></td>
</tr>
<tr>
<td>junit</td>
@@ -291,7 +291,7 @@ h2:hover > .headerlink, h3:hover > .head
</tr>
<tr>
<td>servletapi</td>
-<td>3.0.1+</td>
+<td>3.1.0</td>
<td>Yes</td>
<td>Yes</td>
<td>No</td>
Modified: velocity/site/production/tools/devel/frameworks.html
URL:
http://svn.apache.org/viewvc/velocity/site/production/tools/devel/frameworks.html?rev=1842464&r1=1842463&r2=1842464&view=diff
==============================================================================
--- velocity/site/production/tools/devel/frameworks.html (original)
+++ velocity/site/production/tools/devel/frameworks.html Mon Oct 1 10:26:56
2018
@@ -227,54 +227,62 @@ h2:hover > .headerlink, h3:hover > .head
</ul>
</div>
<h2 id="overview">Overview<a class="headerlink" href="#overview"
title="Permanent link">¶</a></h2>
-<p>VelocityTools is not meant to be a framework in itself, but rather should
ideally be integrated with other frameworks for applications of much size. The
simplest means of integration is to have your framework handle requests,
placing contextual data into the request, session or servlet context attributes
where templates and/or tools can find them, then forward those requests to a
VelocityViewServlet or VelocityLayoutServlet, letting those servlets manage
your VelocityView support for you and render your templates into the response.
If, however, your framework is one like Spring MVC and you either cannot or do
not wish to forward requests to one of the provided servlets, then the
instructions, tips and code below should make it easy for you to integrate
VelocityTools support into your framework of choice.</p>
+<p>This section covers the integration of the Velocity Tools in a J2EE
environment.</p>
+<p>Although VelocityTools can be used without any specific framework, it is
rather meant to be integrated with other frameworks for applications of much
size. The simplest means of integration is to have your framework handle
requests, placing contextual data into the request, session or servlet context
attributes where templates and/or tools can find them, then forward those
requests to a VelocityViewServlet or VelocityLayoutServlet, letting those
servlets manage your VelocityView support for you and render your templates
into the response. If, however, your framework is one like Spring MVC and you
either cannot or do not wish to forward requests to one of the provided
servlets, then the instructions, tips and code below should make it easy for
you to integrate VelocityTools support into your framework of choice.</p>
<h2 id="integration-via-velocityview">Integration Via VelocityView<a
class="headerlink" href="#integration-via-velocityview" title="Permanent
link">¶</a></h2>
<h3 id="configuring">Configuring<a class="headerlink" href="#configuring"
title="Permanent link">¶</a></h3>
<p><a
href="apidocs/org/apache/velocity/tools/view/VelocityView.html">VelocityView</a>
supports the following configuration parameters as application
<context-param>s or as specific servlet <init-param>s in web.xml:</p>
<dl>
-<dt><strong>org.apache.velocity.toolbox</strong></dt>
-<dd>Path and name of the toolbox configuration file. The path must be relative
to the web application root directory. If this parameter is not found, the
servlet will check for a toolbox file at <code>/WEB-INF/tools.xml</code>.</dd>
-<dt><strong>org.apache.velocity.properties</strong></dt>
-<dd>Path and name of the Velocity configuration file. The path must be
relative to the web application root directory. If this parameter is not
present, Velocity will check for a properties file at
<code>/WEB-INF/velocity.properties</code>. If no file is found there, then
Velocity is initialized with the settings in the classpath at
<code>org.apache.velocity.tools.view.velocity.properties</code>.</dd>
-<dt><strong>org.apache.velocity.tools.deprecationSupportMode</strong></dt>
-<dd>Tells VelocityView whether or not it should</dd>
-<dd>
-<ul>
-<li>support old tools that rely on init(Object) methods,</li>
-</ul>
-</dd>
-<dd>
-<ul>
-<li>look for and translate old toolbox.xml configurations, and</li>
-</ul>
-</dd>
-<dd>
-<ul>
-<li>use the deprecated ChainedContext class instead of ViewToolContext.</li>
-</ul>
-</dd>
-<dd>
-<p>By default, this is true, so turn it to false if you want to fully upgrade
to the new systems. Also, specific tools may look for and respect the
deprecationSupportMode setting (e.g. ValueParser, ResourceTool) to provide old
behavior where it has otherwise changed.</p>
-</dd>
-<dt><strong>org.apache.velocity.tools.loadDefaults</strong></dt>
+<dt><strong>org.apache.velocity.properties</strong> =
<code>/WEB-INF/velocity.properties</code></dt>
+<dd>Path and name of the Velocity engine configuration file. The path must be
relative to the web application root directory. First and foremost, the engine
configuration is initialized with default settings found in the classpath at
<code>org.apache.velocity.tools.view.velocity.properties</code>. If this
parameter is not present, Velocity will check for a properties file at
<code>/WEB-INF/velocity.properties</code>.</dd>
+<dt><strong><code>org.apache.velocity.tools</code></strong> =
<code>/WEB-INF/tools.xml</code></dt>
+<dd>Path and name of the tools configuration file. The path must be relative
to the web application root directory. If this parameter is not found, the
servlet will check for a toolbox file at <code>/WEB-INF/tools.xml</code>.</dd>
+<dt><strong><code>org.apache.velocity.tools.loadDefaults</code></strong> =
<code>true</code> | <strong><code>false</code></strong></dt>
<dd>Tells VelocityView whether or not it should include the default tools.xml
configurations provided in the VelocityTools jar(s). This was true by default
in 2.0, it's now false by default.</dd>
-<dt><strong>org.apache.velocity.tools.cleanConfiguration</strong></dt>
+<dt><strong><code>org.apache.velocity.tools.cleanConfiguration</code></strong>
= <code>true</code> | <strong><code>false</code></strong></dt>
<dd>Tells VelocityView to test all the tool configurations and remove any
invalid ones, rather than allow them to throw errors. This is false by
default.</dd>
-<dt><strong>org.apache.velocity.tools.userCanOverwriteTools</strong></dt>
+<dt><strong><code>org.apache.velocity.tools.userCanOverwriteTools</code></strong>
= <strong><code>true</code></strong> | <code>false</code></dt>
<dd>Tells VelocityView to construct the context in such a way that any
user-set variables with the same keys as any of the configured tools are given
primacy when resolving references. This is true by default, unlike in Tools
1.x.</dd>
+<dt><strong><code>org.apache.velocity.tools.shared.config</code></strong> =
<strong><code>true</code></strong> | <code>false</code></dt>
+<dd>At each servlet or filter initialization, if this parameter is false, then
the servlet/filter will own its own VelocityView instance. True by default.</dd>
+<dt><strong><code>org.apache.velocity.tools.view.class</code></strong> =
<code>org.apache.velocity.tools.view.VelocityView</code></dt>
+<dd>Allows to specify a custom class inheriting from VelocityView as the View
class.</dd>
</dl>
-<p>The VelocityView instance is typically the heart of any VelocityTools-using
application. It encapsulates all necessary VelocityEngine and ToolboxFactory
configuration and provides a simple API for processing templates or other VTL
(e.g. VelocityViewTag body content).</p>
+<p>The VelocityView instance is typically the heart of any VelocityTools-using
application. It encapsulates all necessary VelocityEngine and ToolboxFactory
configuration and provides a simple API for processing templates or other
VTL.</p>
<h3 id="retrieving-and-sharing">Retrieving and Sharing<a class="headerlink"
href="#retrieving-and-sharing" title="Permanent link">¶</a></h3>
<p>You can, of course, simply create a VelocityView instance for your
framework to use, but if you are supporting multiple ways of using Velocity
(e.g. VelocityViewTag and separate templates) or if you suspect your users
might want access to the VelocityView facilities, it is better to get your
VelocityView instance using the getVelocityView(...) methods of the
<code>org.apache.velocity.tools.view.ServletUtils</code> class. These methods
will automatically create an instance, store it for you, return it, and then
retrieve it again on subsequent calls to any of those methods. This allows the
VelocityView (which is a rather heavy object) to be shared across multiple
servlets, tags, and filters in the same application. Of course, if you do not
wish to share your VelocityEngine configuration (template cache, global macros)
or Toolbox configuration(s), then you should explicitly avoid using these
methods and construct and manage your own VelocityView instance.</p>
<p>If you are using VelocityViewServlet, VelocityLayoutServlet, and/or
VelocityViewTag in the same application and do not want them to share a
VelocityView instance for some reason, you can tell them to keep their
VelocityViews private by setting
<code>org.apache.velocity.tools.shared.config</code> to <code>false</code> in
the <code>init-param</code>s of the servlet config.</p>
<h3 id="using">Using<a class="headerlink" href="#using" title="Permanent
link">¶</a></h3>
-<p class="note">This is unfinished. <a href="index.html#Contribution">You can
help fix that!</a> - TODO: discuss basic functions, config options, etc
-</p>
+<p>The most basic environment is to bind the VelocityViewServlet to the
extension which pleases you (<code>*.vhtml</code>, <code>*.vm</code>, etc) in
your <code>/WEB-INF/web.xml</code> file:</p>
+<div class="codehilite"><pre><span class="cp"><?xml version="1.0"
encoding="UTF-8" ?></span>
+<span class="nt"><web-app</span>
+ <span class="na">xmlns=</span><span
class="s">"http://java.sun.com/xml/ns/javaee"</span>
+ <span class="na">xmlns:xsi=</span><span
class="s">"http://www.w3.org/2001/XMLSchema-instance"</span>
+ <span class="na">xsi:schemaLocation=</span><span
class="s">"http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"</span>
+ <span class="na">metadata-complete=</span><span
class="s">"false"</span>
+ <span class="na">version=</span><span class="s">"3.0"</span><span
class="nt">></span>
+ <span class="nt"><servlet></span>
+ <span class="nt"><servlet-name></span>view<span
class="nt"></servlet-name></span>
+ <span class="nt"><servlet-class></span>servlet.ViewServlet<span
class="nt"></servlet-class></span>
+ <span class="nt"><load-on-startup></span>1<span
class="nt"></load-on-startup></span>
+ <span class="nt"></servlet></span>
+ <span class="nt"><servlet-mapping></span>
+ <span class="nt"><servlet-name></span>view<span
class="nt"></servlet-name></span>
+ <span class="nt"><url-pattern></span>*.vhtml<span
class="nt"></url-pattern></span>
+ <span class="nt"></servlet-mapping></span>
+<span class="nt"></web-app></span>
+</pre></div>
+
+
+<p>Then, you would of course add some tools, either by providing a
<code>/WEB-INF/tools.xml</code> file or by enabling default tools (by means of
the <code>org.apache.velocity.tools.loadDefaults</code> configuration parameter
described above), or both. In the later case, your custom tools configuration
will overwrite the default ones.</p>
+<p>You can easily use a custom subclass of the <a
href="apidocs/org/apache/velocity/tools/view/VelocityViewServlet.html">VelocityViewServlet</a>
and override its methods, amongs which but not limited to:
<code>createContext(request, response)</code>, <code>fillContext(context,
request)</code>, <code>getTempate(request, response)</code>,
<code>setContentType()</code>.</p>
+<p>You can also override the <a
href="apidocs/org/apache/velocity/tools/view/VelocityViewServlet.html">VelocityView</a>
class, which gives a wider range of subclassing options. You can do so by
providing a custom VelocityView class name tp the
<code>org.apache.velocity.tools.view.class</code> init (at the servlet/filter
level) or config (at the webapp level) parameter, see above.</p>
+<p>Be sure to check the tools integration mechanism described in the <a
href="creating-tools.html">creating tools</a> section to see how the
configuration, your custom view and your custom tools do interact.</p>
<h2 id="other-ways-to-integrate-velocitytools">Other Ways to Integrate
VelocityTools<a class="headerlink"
href="#other-ways-to-integrate-velocitytools" title="Permanent
link">¶</a></h2>
<h3 id="toolboxfactory">ToolboxFactory<a class="headerlink"
href="#toolboxfactory" title="Permanent link">¶</a></h3>
<p>This is unfinished. <a href="index.html#Contribution">You can help fix
that!</a> - TODO: Discuss lifecycle, configuration, and use. See <a
href="http://velocity.markmail.org/search/?q=subject%3A%22upgrading%22#query:subject%3Aupgrading%20order%3Adate-forward+page:3+mid:pw56jxgsudhwwnnd+state:results";>this
email thread</a> for more on this, including code samples.</p>
<h3 id="standalone-use">Standalone Use<a class="headerlink"
href="#standalone-use" title="Permanent link">¶</a></h3>
-<p>The so-called "standalone" methods of tool use developed from a desire to
<a href="standalone.html#Just_Use_Them!">use tools directly</a>, particularly
the GenericTools which had no servlet dependencies. However, now many
VelocityView tools can also be used "standalone" with varying degrees of effort
and no need to create any VelocityView instances. Most of the time, you just
treat them like any other POJO--create an instance, provide any need
values/objects and use it.</p>
+<p>The so-called "standalone" methods of tool use developed from a desire to
<a href="standalone.html#Just_Use_Them">use tools directly</a>, particularly
the GenericTools which had no servlet dependencies. However, now many
VelocityView tools can also be used "standalone" with varying degrees of effort
and no need to create any VelocityView instances. Most of the time, you just
treat them like any other POJO--create an instance, provide any need
values/objects and use it.</p>
<p>If you want a little more help with things, consider using a <a
href="standalone.html#ToolManager">ToolManager</a>.</p></div></div>
<hr/>
<div id="copyright">
Modified: velocity/site/production/tools/devel/generic.html
URL:
http://svn.apache.org/viewvc/velocity/site/production/tools/devel/generic.html?rev=1842464&r1=1842463&r2=1842464&view=diff
==============================================================================
--- velocity/site/production/tools/devel/generic.html (original)
+++ velocity/site/production/tools/devel/generic.html Mon Oct 1 10:26:56 2018
@@ -210,6 +210,17 @@ h2:hover > .headerlink, h3:hover > .head
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
<h2 id="overview">Overview<a class="headerlink" href="#overview"
title="Permanent link">¶</a></h2>
<p>GenericTools is the set of classes that provide basic infrastructure for
using tools in standard Java SE Velocity projects, as well as a set of tools
for use in generic Velocity templates. These tools have no Java EE dependencies
and are often safe to use as "singletons". Some of them are not thread-safe to
allow both a no-arg constructor and configurability, but the state-changing
methods are declared protected with the exception of configure(Map) which
is--by default--rendered useless after being used just once. If you require
strict thread-safety, be cautious in using any configurable tools and consider
<a
href="http://wiki.apache.org/velocity/BuildingSecureWebApplications";>restricting
the abilities of template authors</a> to prevent circumvention of the lockdown
placed on configuration methods.</p>
+<h2 id="installation">Installation<a class="headerlink" href="#installation"
title="Permanent link">¶</a></h2>
+<p>For inclusion in a Maven project, use the following dependency block:</p>
+<div class="codehilite"><pre><span class="nt"><dependency></span>
+ <span class="nt"><groupId></span>org.apache.velocity.tools<span
class="nt"></groupId></span>
+ <span class="nt"><artifactId></span>velocity-tools-generic<span
class="nt"></artifactId></span>
+ <span class="nt"><version></span>3.0<span
class="nt"></version></span>
+<span class="nt"></dependency></span>
+</pre></div>
+
+
+<p>Otherwise, see the <a href="/download.html#tools">download page</a> for how
to get the Velocity Generic Tools jar.</p>
<h2 id="usage">Usage<a class="headerlink" href="#usage" title="Permanent
link">¶</a></h2>
<ul>
<li>
Modified: velocity/site/production/tools/devel/index.html
URL:
http://svn.apache.org/viewvc/velocity/site/production/tools/devel/index.html?rev=1842464&r1=1842463&r2=1842464&view=diff
==============================================================================
--- velocity/site/production/tools/devel/index.html (original)
+++ velocity/site/production/tools/devel/index.html Mon Oct 1 10:26:56 2018
@@ -219,8 +219,10 @@ h2:hover > .headerlink, h3:hover > .head
<h2 id="whats-new-in-30">What's new in 3.0<a class="headerlink"
href="#whats-new-in-30" title="Permanent link">¶</a></h2>
<p>Velocity Tools 3.0 new features:</p>
<ul>
-<li>A <a href="maven-velocity-tools-plugin/index.html">Maven plugin</a> to
allow embedding of JSP tag libraries inside Velocity templates.</li>
+<li>New generic <a
href="apidocs/org/apache/velocity/tools/generic/CollectionTool.html">CollectionTool</a>
which replaces and enhances the former SortTool.</li>
+<li>New generic <a
href="apidocs/org/apache/velocity/tools/generic/JsonTool.html">JsonTool</a> and
view <a
href="apidocs/org/apache/velocity/tools/view/JsonTool.html">JsonTool</a>.</li>
<li>New generic <a
href="apidocs/org/apache/velocity/tools/generic/LogTool.html">LogTool</a>.</li>
+<li>A <a href="maven-velocity-tools-plugin/index.html">Maven plugin</a> to
allow embedding of JSP tag libraries inside Velocity templates.</li>
</ul>
<p>See the <a href="upgrading.html">Upgrading section</a> for a complete list
of changes.</p>
<h2 id="why-20">Why 2.0?<a class="headerlink" href="#why-20" title="Permanent
link">¶</a></h2>
Modified: velocity/site/production/tools/devel/upgrading.html
URL:
http://svn.apache.org/viewvc/velocity/site/production/tools/devel/upgrading.html?rev=1842464&r1=1842463&r2=1842464&view=diff
==============================================================================
--- velocity/site/production/tools/devel/upgrading.html (original)
+++ velocity/site/production/tools/devel/upgrading.html Mon Oct 1 10:26:56 2018
@@ -225,6 +225,7 @@ h2:hover > .headerlink, h3:hover > .head
</ul>
</div>
<h2 id="upgrading-to-30">Upgrading to 3.0<a class="headerlink"
href="#upgrading-to-30" title="Permanent link">¶</a></h2>
+<p>The maven <code>groupId</code> has been changed to
<code>org.apache.velocity.tools</code> .</p>
<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>
<p>All objects, methods and configuration formats deprecated in 2.0 have been
suppressed.</p>
<p>Support for the Struts 1.x tools has been discontinued.</p>
Modified: velocity/site/production/tools/devel/view.html
URL:
http://svn.apache.org/viewvc/velocity/site/production/tools/devel/view.html?rev=1842464&r1=1842463&r2=1842464&view=diff
==============================================================================
--- velocity/site/production/tools/devel/view.html (original)
+++ velocity/site/production/tools/devel/view.html Mon Oct 1 10:26:56 2018
@@ -218,6 +218,17 @@ h2:hover > .headerlink, h3:hover > .head
<li>A number of useful, extendable tools for developing web applications are
already provided for your convenience.</li>
<li>Logging is made through the SLF4J logging facade. It can be directed to
the log infrastructure of the Web application (using the logging facility
provided by the Servlet API) by addind the <a
href="https://github.com/arkanovicz/webapp-slf4j-logger";>webapp slf4j
logger</a> into the classpath. </li>
</ul>
+<h2 id="installation">Installation<a class="headerlink" href="#installation"
title="Permanent link">¶</a></h2>
+<p>For inclusion in a Maven project, use the following dependency block:</p>
+<div class="codehilite"><pre><span class="nt"><dependency></span>
+ <span class="nt"><groupId></span>org.apache.velocity.tools<span
class="nt"></groupId></span>
+ <span class="nt"><artifactId></span>velocity-tools-view<span
class="nt"></artifactId></span>
+ <span class="nt"><version></span>3.0<span
class="nt"></version></span>
+<span class="nt"></dependency></span>
+</pre></div>
+
+
+<p>Otherwise, see the <a href="/download.html#tools">download page</a> for how
to get the Velocity View Tools jar.</p>
<h2 id="default-configuration">Default Configuration<a class="headerlink"
href="#default-configuration" title="Permanent link">¶</a></h2>
<p>The default configuration provided for VelocityView is <a
href="http://svn.apache.org/viewvc/velocity/tools/trunk/velocity-tools-generic/src/main/resources/org/apache/velocity/tools/generic/tools.xml?view=markup"";>here</a>
and <a
href="http://svn.apache.org/viewvc/velocity/tools/trunk/velocity-tools-view/src/main/resources/org/apache/velocity/tools/view/tools.xml?view=markup";>here</a>.</p>
<h2 id="dependencies">Dependencies<a class="headerlink" href="#dependencies"
title="Permanent link">¶</a></h2>
Modified: velocity/site/production/who-we-are.html
URL:
http://svn.apache.org/viewvc/velocity/site/production/who-we-are.html?rev=1842464&r1=1842463&r2=1842464&view=diff
==============================================================================
--- velocity/site/production/who-we-are.html (original)
+++ velocity/site/production/who-we-are.html Mon Oct 1 10:26:56 2018
@@ -294,6 +294,13 @@ h2:hover > .headerlink, h3:hover > .head
<td/>
<td>PMC Member</td>
</tr>
+ <tr>
+ <td>Michael Osipov</td>
+ <td>michaelo</td>
+ <td>[email protected]</td>
+ <td/>
+ <td>PMC Member</td>
+ </tr>
</tbody>
</table>
<h2 xmlns:pom="http://maven.apache.org/POM/4.0.0";>Apache Velocity
Commiters</h2><table xmlns:pom="http://maven.apache.org/POM/4.0.0";
class="standard">
@@ -377,6 +384,13 @@ h2:hover > .headerlink, h3:hover > .head
<td/>
<td/>
</tr>
+ <tr>
+ <td>Michael Osipov</td>
+ <td>michaelo</td>
+ <td>[email protected]</td>
+ <td/>
+ <td/>
+ </tr>
</tbody>
</table>
<h2 xmlns:pom="http://maven.apache.org/POM/4.0.0";>Velocity Emeriti</h2><table
xmlns:pom="http://maven.apache.org/POM/4.0.0"; class="standard">
