You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@yetus.apache.org by aw...@apache.org on 2016/02/27 00:18:14 UTC
[6/9] yetus git commit: git hash
c533842b47c9c113f4bdef5a0a7005cf1b9c4de1
http://git-wip-us.apache.org/repos/asf/yetus/blob/d709aeb5/documentation/0.1.0/precommit-apidocs/smart-apply-patch/index.html
----------------------------------------------------------------------
diff --git a/documentation/0.1.0/precommit-apidocs/smart-apply-patch/index.html b/documentation/0.1.0/precommit-apidocs/smart-apply-patch/index.html
index 691c406..81c0b90 100644
--- a/documentation/0.1.0/precommit-apidocs/smart-apply-patch/index.html
+++ b/documentation/0.1.0/precommit-apidocs/smart-apply-patch/index.html
@@ -136,14 +136,15 @@
<hr>
-<h2 id="public-stable-not-replaceable">Public/Stable/Not Replaceable</h2>
+<h2>Public/Stable/Not Replaceable</h2>
-<h3 id="setup_defaults"><code>setup_defaults</code></h3>
+<h3><code>setup_defaults</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>setup_defaults
+
+<pre><code>setup_defaults
</code></pre>
<ul>
@@ -157,14 +158,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -177,13 +175,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="yetus_usage"><code>yetus_usage</code></h3>
+<h3><code>yetus_usage</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>yetus_usage
+
+<pre><code>yetus_usage
</code></pre>
<ul>
@@ -197,14 +195,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -217,15 +212,15 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
+<h2>None/None/Not Replaceable</h2>
-<h2 id="none-none-not-replaceable">None/None/Not Replaceable</h2>
-
-<h3 id="add_footer_table"><code>add_footer_table</code></h3>
+<h3><code>add_footer_table</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>add_footer_table
+
+<pre><code>add_footer_table
</code></pre>
<ul>
@@ -239,14 +234,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">None</td>
</tr>
@@ -259,13 +251,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="add_test"><code>add_test</code></h3>
+<h3><code>add_test</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>add_test
+
+<pre><code>add_test
</code></pre>
<ul>
@@ -279,14 +271,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">None</td>
</tr>
@@ -299,13 +288,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="add_vote_table"><code>add_vote_table</code></h3>
+<h3><code>add_vote_table</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>add_vote_table
+
+<pre><code>add_vote_table
</code></pre>
<ul>
@@ -319,14 +308,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">None</td>
</tr>
@@ -339,13 +325,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="big_console_header"><code>big_console_header</code></h3>
+<h3><code>big_console_header</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>big_console_header
+
+<pre><code>big_console_header
</code></pre>
<ul>
@@ -359,14 +345,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">None</td>
</tr>
@@ -379,7 +362,6 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
</div>
<div class="container">
<hr>
@@ -387,7 +369,7 @@
<div class="row-fluid">
<div class="span12 text-left">
<div class="span12">
- Copyright 2008-2015 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
+ Copyright 2008-2016 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
</div>
</div>
http://git-wip-us.apache.org/repos/asf/yetus/blob/d709aeb5/documentation/0.1.0/precommit-apidocs/test-patch/index.html
----------------------------------------------------------------------
diff --git a/documentation/0.1.0/precommit-apidocs/test-patch/index.html b/documentation/0.1.0/precommit-apidocs/test-patch/index.html
index 8e1b3df..5caa814 100644
--- a/documentation/0.1.0/precommit-apidocs/test-patch/index.html
+++ b/documentation/0.1.0/precommit-apidocs/test-patch/index.html
@@ -179,14 +179,15 @@
<hr>
-<h2 id="public-stable-replaceable">Public/Stable/Replaceable</h2>
+<h2>Public/Stable/Replaceable</h2>
-<h3 id="relative_dir"><code>relative_dir</code></h3>
+<h3><code>relative_dir</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>relative_dir path
+
+<pre><code>relative_dir path
</code></pre>
<ul>
@@ -202,14 +203,11 @@
<p>1 - no, path</p>
<p>0 - yes, path - BASEDIR</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -222,13 +220,13 @@
<td style="text-align: left">Yes</td>
</tr>
</tbody></table>
-
-<h3 id="verify_multijdk_test"><code>verify_multijdk_test</code></h3>
+<h3><code>verify_multijdk_test</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>verify_multijdk_test test
+
+<pre><code>verify_multijdk_test test
</code></pre>
<ul>
@@ -244,14 +242,11 @@
<p>1 = yes</p>
<p>0 = no</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -264,15 +259,15 @@
<td style="text-align: left">Yes</td>
</tr>
</tbody></table>
+<h2>Public/Stable/Not Replaceable</h2>
-<h2 id="public-stable-not-replaceable">Public/Stable/Not Replaceable</h2>
-
-<h3 id="add_footer_table"><code>add_footer_table</code></h3>
+<h3><code>add_footer_table</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>add_footer_table subsystem string
+
+<pre><code>add_footer_table subsystem string
</code></pre>
<ul>
@@ -286,14 +281,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -306,13 +298,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="add_header_line"><code>add_header_line</code></h3>
+<h3><code>add_header_line</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>add_header_line string
+
+<pre><code>add_header_line string
</code></pre>
<ul>
@@ -326,14 +318,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -346,13 +335,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="add_test_table"><code>add_test_table</code></h3>
+<h3><code>add_test_table</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>add_test_table failurereason testlist
+
+<pre><code>add_test_table failurereason testlist
</code></pre>
<ul>
@@ -366,14 +355,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -386,13 +372,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="add_vote_table"><code>add_vote_table</code></h3>
+<h3><code>add_vote_table</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>add_vote_table +1/0/-1/null subsystem string
+
+<pre><code>add_vote_table +1/0/-1/null subsystem string
</code></pre>
<ul>
@@ -406,14 +392,11 @@
</ul>
<p>Elapsed time display</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -426,13 +409,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="big_console_header"><code>big_console_header</code></h3>
+<h3><code>big_console_header</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>big_console_header string
+
+<pre><code>big_console_header string
</code></pre>
<ul>
@@ -446,14 +429,11 @@
</ul>
<p>large chunk of text</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -466,13 +446,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="clock_display"><code>clock_display</code></h3>
+<h3><code>clock_display</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>clock_display seconds
+
+<pre><code>clock_display seconds
</code></pre>
<ul>
@@ -486,14 +466,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -506,13 +483,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="echo_and_redirect"><code>echo_and_redirect</code></h3>
+<h3><code>echo_and_redirect</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>echo_and_redirect filename command [..]
+
+<pre><code>echo_and_redirect filename command [..]
</code></pre>
<ul>
@@ -526,14 +503,11 @@
</ul>
<p>$?</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -546,13 +520,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="generate_stack"><code>generate_stack</code></h3>
+<h3><code>generate_stack</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>generate_stack
+
+<pre><code>generate_stack
</code></pre>
<ul>
@@ -566,14 +540,11 @@
</ul>
<p>exits</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -586,13 +557,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="module_file_fragment"><code>module_file_fragment</code></h3>
+<h3><code>module_file_fragment</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>module_file_fragment module
+
+<pre><code>module_file_fragment module
</code></pre>
<ul>
@@ -606,14 +577,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -626,13 +594,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="offset_clock"><code>offset_clock</code></h3>
+<h3><code>offset_clock</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>offset_clock seconds
+
+<pre><code>offset_clock seconds
</code></pre>
<ul>
@@ -646,14 +614,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -666,13 +631,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="setup_defaults"><code>setup_defaults</code></h3>
+<h3><code>setup_defaults</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>setup_defaults
+
+<pre><code>setup_defaults
</code></pre>
<ul>
@@ -686,14 +651,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -706,13 +668,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="start_clock"><code>start_clock</code></h3>
+<h3><code>start_clock</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>start_clock
+
+<pre><code>start_clock
</code></pre>
<ul>
@@ -726,14 +688,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -746,13 +705,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="stop_clock"><code>stop_clock</code></h3>
+<h3><code>stop_clock</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>stop_clock
+
+<pre><code>stop_clock
</code></pre>
<ul>
@@ -766,14 +725,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -786,13 +742,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="write_comment"><code>write_comment</code></h3>
+<h3><code>write_comment</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>write_comment filename
+
+<pre><code>write_comment filename
</code></pre>
<ul>
@@ -806,14 +762,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -826,13 +779,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="yetus_usage"><code>yetus_usage</code></h3>
+<h3><code>yetus_usage</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>yetus_usage
+
+<pre><code>yetus_usage
</code></pre>
<ul>
@@ -846,14 +799,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -866,36 +816,33 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
+<h2>Public/Evolving/Not Replaceable</h2>
-<h2 id="public-evolving-not-replaceable">Public/Evolving/Not Replaceable</h2>
-
-<h3 id="bugsystem_linecomments"><code>bugsystem_linecomments</code></h3>
+<h3><code>bugsystem_linecomments</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>bugsystem_linecomments filename
+
+<pre><code>bugsystem_linecomments filename
</code></pre>
<ul>
<li>Description</li>
</ul>
-<p>Write comments onto bug systems that have code review support. File should be in the form of “file:line:comment”</p>
+<p>Write comments onto bug systems that have code review support. File should be in the form of <q>file:line:comment</q></p>
<ul>
<li>Returns</li>
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -908,13 +855,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="calcdiffs"><code>calcdiffs</code></h3>
+<h3><code>calcdiffs</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>calcdiffs
+
+<pre><code>calcdiffs
</code></pre>
<ul>
@@ -928,14 +875,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -948,13 +892,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="clear_personality_queue"><code>clear_personality_queue</code></h3>
+<h3><code>clear_personality_queue</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>clear_personality_queue
+
+<pre><code>clear_personality_queue
</code></pre>
<ul>
@@ -968,14 +912,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -988,13 +929,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="compile"><code>compile</code></h3>
+<h3><code>compile</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>compile branch|patch
+
+<pre><code>compile branch|patch
</code></pre>
<ul>
@@ -1010,14 +951,11 @@
<p>0 on success</p>
<p>1 on failure</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -1030,13 +968,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="compile_cycle"><code>compile_cycle</code></h3>
+<h3><code>compile_cycle</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>compile_cycle branch|patch
+
+<pre><code>compile_cycle branch|patch
</code></pre>
<ul>
@@ -1052,14 +990,11 @@
<p>0 on success</p>
<p>1 on failure</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -1072,13 +1007,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="distclean"><code>distclean</code></h3>
+<h3><code>distclean</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>distclean
+
+<pre><code>distclean
</code></pre>
<ul>
@@ -1094,14 +1029,11 @@
<p>0 on success</p>
<p>1 on failure</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -1114,13 +1046,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="generic_logfilter"><code>generic_logfilter</code></h3>
+<h3><code>generic_logfilter</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>generic_logfilter
+
+<pre><code>generic_logfilter
</code></pre>
<ul>
@@ -1134,14 +1066,11 @@
</ul>
<p>number of issues</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -1154,13 +1083,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="generic_post_handler"><code>generic_post_handler</code></h3>
+<h3><code>generic_post_handler</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>generic_post_handler origlog testtype multijdkmode run commands
+
+<pre><code>generic_post_handler origlog testtype multijdkmode run commands
</code></pre>
<ul>
@@ -1176,14 +1105,11 @@
<p>0 on success</p>
<p>1 on failure</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -1196,13 +1122,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="generic_postlog_compare"><code>generic_postlog_compare</code></h3>
+<h3><code>generic_postlog_compare</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>generic_postlog_compare origlog testtype multijdkmode
+
+<pre><code>generic_postlog_compare origlog testtype multijdkmode
</code></pre>
<ul>
@@ -1218,14 +1144,11 @@
<p>0 on success</p>
<p>1 on failure</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -1238,13 +1161,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="generic_pre_handler"><code>generic_pre_handler</code></h3>
+<h3><code>generic_pre_handler</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>generic_pre_handler testype multijdk
+
+<pre><code>generic_pre_handler testype multijdk
</code></pre>
<ul>
@@ -1260,14 +1183,11 @@
<p>1 on failure</p>
<p>0 on success</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -1280,13 +1200,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="initialize"><code>initialize</code></h3>
+<h3><code>initialize</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>initialize $@
+
+<pre><code>initialize $@
</code></pre>
<ul>
@@ -1302,14 +1222,11 @@
<p>0 on success</p>
<p>1 on failure</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -1322,13 +1239,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="module_status"><code>module_status</code></h3>
+<h3><code>module_status</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>module_status module runtime
+
+<pre><code>module_status module runtime
</code></pre>
<ul>
@@ -1342,14 +1259,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -1362,13 +1276,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="modules_messages"><code>modules_messages</code></h3>
+<h3><code>modules_messages</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>modules_messages repostatus testtype mvncmdline
+
+<pre><code>modules_messages repostatus testtype mvncmdline
</code></pre>
<ul>
@@ -1382,14 +1296,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -1402,13 +1313,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="modules_reset"><code>modules_reset</code></h3>
+<h3><code>modules_reset</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>modules_reset
+
+<pre><code>modules_reset
</code></pre>
<ul>
@@ -1422,14 +1333,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -1442,13 +1350,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="modules_workers"><code>modules_workers</code></h3>
+<h3><code>modules_workers</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>modules_workers repostatus testtype mvncmdline
+
+<pre><code>modules_workers repostatus testtype mvncmdline
</code></pre>
<ul>
@@ -1462,14 +1370,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -1482,13 +1387,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="patchfiletests"><code>patchfiletests</code></h3>
+<h3><code>patchfiletests</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>patchfiletests branch|patch
+
+<pre><code>patchfiletests branch|patch
</code></pre>
<ul>
@@ -1504,14 +1409,11 @@
<p>0 on success</p>
<p>1 on failure</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -1524,13 +1426,13 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
-
-<h3 id="personality_enqueue_module"><code>personality_enqueue_module</code></h3>
+<h3><code>personality_enqueue_module</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>personality_enqueue_module module profiles/flags/etc
+
+<pre><code>personality_enqueue_module module profiles/flags/etc
</code></pre>
<ul>
@@ -1544,14 +1446,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Public</td>
</tr>
@@ -1564,15 +1463,15 @@
<td style="text-align: left">No</td>
</tr>
</tbody></table>
+<h2>Private/Stable/Replaceable</h2>
-<h2 id="private-stable-replaceable">Private/Stable/Replaceable</h2>
-
-<h3 id="prepopulate_footer"><code>prepopulate_footer</code></h3>
+<h3><code>prepopulate_footer</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>prepopulate_footer
+
+<pre><code>prepopulate_footer
</code></pre>
<ul>
@@ -1586,14 +1485,11 @@
</ul>
<p>Nothing</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Private</td>
</tr>
@@ -1606,13 +1502,13 @@
<td style="text-align: left">Yes</td>
</tr>
</tbody></table>
-
-<h3 id="report_jvm_version"><code>report_jvm_version</code></h3>
+<h3><code>report_jvm_version</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>report_jvm_version directory
+
+<pre><code>report_jvm_version directory
</code></pre>
<ul>
@@ -1626,14 +1522,11 @@
</ul>
<p>version</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Private</td>
</tr>
@@ -1646,15 +1539,15 @@
<td style="text-align: left">Yes</td>
</tr>
</tbody></table>
+<h2>Private/Evolving/Replaceable</h2>
-<h2 id="private-evolving-replaceable">Private/Evolving/Replaceable</h2>
-
-<h3 id="verify_patchdir_still_exists"><code>verify_patchdir_still_exists</code></h3>
+<h3><code>verify_patchdir_still_exists</code></h3>
<ul>
<li>Synopsis</li>
</ul>
-<pre class="highlight plaintext"><code>verify_patchdir_still_exists
+
+<pre><code>verify_patchdir_still_exists
</code></pre>
<ul>
@@ -1668,14 +1561,11 @@
</ul>
<p>may exit on failure</p>
-
-<table><thead>
-<tr>
+<table class='table table-bordered table-striped'><thead><tr>
<th style="text-align: left">Classification</th>
<th style="text-align: left">Level</th>
</tr>
-</thead><tbody>
-<tr>
+</thead><tbody><tr>
<td style="text-align: left">Audience</td>
<td style="text-align: left">Private</td>
</tr>
@@ -1688,7 +1578,6 @@
<td style="text-align: left">Yes</td>
</tr>
</tbody></table>
-
</div>
<div class="container">
<hr>
@@ -1696,7 +1585,7 @@
<div class="row-fluid">
<div class="span12 text-left">
<div class="span12">
- Copyright 2008-2015 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
+ Copyright 2008-2016 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
</div>
</div>
http://git-wip-us.apache.org/repos/asf/yetus/blob/d709aeb5/documentation/0.1.0/precommit-architecture/index.html
----------------------------------------------------------------------
diff --git a/documentation/0.1.0/precommit-architecture/index.html b/documentation/0.1.0/precommit-architecture/index.html
index 4ef1388..2b8d94d 100644
--- a/documentation/0.1.0/precommit-architecture/index.html
+++ b/documentation/0.1.0/precommit-architecture/index.html
@@ -118,10 +118,10 @@
under the License.
-->
-<h1 id="some-philosophy">Some Philosophy</h1>
+<h1>Some Philosophy</h1>
<ul>
-<li><p>Everyone’s time is valuable. The quicker contributors can get feedback and iterate, the more likely and faster their contribution will get checked in. A committer should be able to focus on the core issues of a contribution rather than details that can be determined automatically.</p></li>
+<li><p>Everyone's time is valuable. The quicker contributors can get feedback and iterate, the more likely and faster their contribution will get checked in. A committer should be able to focus on the core issues of a contribution rather than details that can be determined automatically.</p></li>
<li><p>Precommit checks should be fast. There is no value in testing parts of the source tree that are not immediately impacted by a change. Unit testing is the target. They are not a replacement for full builds or integration tests.</p></li>
<li><p>Many open source projects have a desire to have this capability. Why not generalize a solution?</p></li>
<li><p>In many build systems (especially with maven), a modular design has been picked. Why not leverage that design to make checks faster?</p></li>
@@ -129,11 +129,11 @@
<li><p>Portability matters. Tooling should be as operating system and language agnostic as possible.</p></li>
</ul>
-<h1 id="phases">Phases</h1>
+<h1>Phases</h1>
<p>test-patch works effectively under several different phases:</p>
-<h2 id="initialize">Initialize</h2>
+<h2>Initialize</h2>
<p>This is where test-patch configures and validates the environment. Some things done in this phase:</p>
@@ -147,17 +147,17 @@
<li>git repository management (fresh pull, branch switching, etc)</li>
</ul>
-<h2 id="precheck">Precheck</h2>
+<h2>Precheck</h2>
<p>Checks done here are <em>fatal</em>.</p>
<p>This acts as a verification of all of the setup parts and is the final place to short-cut the full test cycle. The most significant built-in check done here is verifying the patch file is a valid.</p>
-<h2 id="patch-file-tests">Patch File Tests</h2>
+<h2>Patch File Tests</h2>
<p>Tests that only require the patch file are run. Note that the repository is still from the initial checkout!</p>
-<h2 id="compile-cycle-branch">Compile Cycle (Branch)</h2>
+<h2>Compile Cycle (Branch)</h2>
<p>When compilation must be done, we follow these five steps:</p>
@@ -169,7 +169,7 @@
<li>A rebuild phase to run tests that require recompiles</li>
</ul>
-<p>The first time this is done is with the pristine checkout. This is called the “branch compile”. For this pass, this is where the ‘before’ work is handled. Some things that typically get checked in this phase:</p>
+<p>The first time this is done is with the pristine checkout. This is called the <q>branch compile</q>. For this pass, this is where the 'before' work is handled. Some things that typically get checked in this phase:</p>
<ul>
<li>The first pass of files and modules that will get patched</li>
@@ -177,27 +177,27 @@
<li>javadoc, scaladoc, etc</li>
</ul>
-<h2 id="distribution-clean">Distribution Clean</h2>
+<h2>Distribution Clean</h2>
<p>This step is to wipe the repository clean back to a pristine state such that the previous cycle will not impact the next cycle.</p>
-<h2 id="patch-application">Patch Application</h2>
+<h2>Patch Application</h2>
<p>The patch gets applied.</p>
-<h2 id="compile-cycle-patch">Compile Cycle (Patch)</h2>
+<h2>Compile Cycle (Patch)</h2>
-<p>Now that the patch has been applied the steps to compile we outlined in the compilation (branch) phase are repeated but with the patch applied. This is where a lot of 'after’ checks are performed.</p>
+<p>Now that the patch has been applied the steps to compile we outlined in the compilation (branch) phase are repeated but with the patch applied. This is where a lot of 'after' checks are performed.</p>
-<h2 id="unit-tests">Unit Tests</h2>
+<h2>Unit Tests</h2>
<p>Since unit tests are generally the slowest part of the precommit process, they are run last. At this point, all the prerequisites to running them should be in place and ready to go.</p>
-<h2 id="reporting">Reporting</h2>
+<h2>Reporting</h2>
<p>Finally, the results are reported to the screen and, optionally, to JIRA and/or whatever bug system has been configured.</p>
-<h1 id="test-flow">Test Flow</h1>
+<h1>Test Flow</h1>
<p>The basic workflow for many of the sub-items in individual phases are:</p>
@@ -219,7 +219,7 @@
<div class="row-fluid">
<div class="span12 text-left">
<div class="span12">
- Copyright 2008-2015 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
+ Copyright 2008-2016 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
</div>
</div>
http://git-wip-us.apache.org/repos/asf/yetus/blob/d709aeb5/documentation/0.1.0/precommit-basic/index.html
----------------------------------------------------------------------
diff --git a/documentation/0.1.0/precommit-basic/index.html b/documentation/0.1.0/precommit-basic/index.html
index befeecd..a9012e3 100644
--- a/documentation/0.1.0/precommit-basic/index.html
+++ b/documentation/0.1.0/precommit-basic/index.html
@@ -118,7 +118,7 @@
under the License.
-->
-<h1 id="test-patch">test-patch</h1>
+<h1>test-patch</h1>
<ul>
<li><a href="#Purpose">Purpose</a></li>
@@ -131,27 +131,27 @@
<li><a href="#Docker">Docker</a></li>
</ul>
-<h1 id="purpose">Purpose</h1>
+<h1>Purpose</h1>
-<p>As part of Apache Hadoop’s commit process, all patches to the source base go through a precommit test that does some (relatively) light checking to make sure the proposed change does not break unit tests and/or passes some other prerequisites such as code formatting guidelines. This is meant as a preliminary check for committers so that the basic patch is in a known state and for contributors to know if they have followed the project’s guidelines. This check, called test-patch, along with a helper program, called smart-apply-patch, may also be used by individual developers to verify a patch prior to sending to the Apache Hadoop QA systems.</p>
+<p>As part of Apache Hadoop's commit process, all patches to the source base go through a precommit test that does some (relatively) light checking to make sure the proposed change does not break unit tests and/or passes some other prerequisites such as code formatting guidelines. This is meant as a preliminary check for committers so that the basic patch is in a known state and for contributors to know if they have followed the project's guidelines. This check, called test-patch, along with a helper program, called smart-apply-patch, may also be used by individual developers to verify a patch prior to sending to the Apache Hadoop QA systems.</p>
-<p>Other projects have adopted a similar methodology after seeing great success in the Apache Hadoop model. Some have even gone as far as forking Apache Hadoop’s precommit code and modifying it to meet their project’s needs.</p>
+<p>Other projects have adopted a similar methodology after seeing great success in the Apache Hadoop model. Some have even gone as far as forking Apache Hadoop's precommit code and modifying it to meet their project's needs.</p>
<p>One of the key facets of Apache Yetus is to bring together all of these forks under a common code base to help software development
as a whole.</p>
-<h1 id="pre-requisites">Pre-requisites</h1>
+<h1>Pre-requisites</h1>
<p>test-patch and smart-apply-patch are written in bash for maximum portability. As such, it mostly assumes the locations of commands to be in the file path. However, in many cases, this assumption may be overridden via command line options.</p>
<p>For Solaris and Solaris-like operating systems, the default location for the POSIX binaries is in /usr/xpg4/bin and the default location for the GNU binaries is /usr/gnu/bin.</p>
-<h2 id="base-requirements">Base Requirements</h2>
+<h2>Base Requirements</h2>
<p>test-patch requires these installed components to execute:</p>
<ul>
-<li>A project with a supported build tool (ant, gradle, maven, …)</li>
+<li>A project with a supported build tool (ant, gradle, maven, ...)</li>
<li>git-based project (and git 1.7.3 or higher installed)</li>
<li>bash v3.2 or higher</li>
<li>GNU diff</li>
@@ -163,7 +163,7 @@ as a whole.</p>
<li>file command</li>
</ul>
-<h2 id="optional-requirements">Optional Requirements</h2>
+<h2>Optional Requirements</h2>
<p>Features are plug-in based and enabled either individually or collectively on the command line. From there, these are activated based upon tool availability, the languages being tested, etc. The external dependencies of plug-ins may have different licensing requirements than Apache Yetus.</p>
@@ -194,148 +194,167 @@ as a whole.</p>
<li><a href="https://github.com/koalaman/shellcheck">shellcheck</a> installed, preferably 0.3.6 or higher</li>
</ul>
-<h1 id="basic-usage">Basic Usage</h1>
+<h1>Basic Usage</h1>
<p>The first step for a successful deployment is determining which features/plug-ins to enable:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh --list-plugins
+
+<pre><code class="bash">$ test-patch.sh --list-plugins
</code></pre>
<p>This option will list all of the available plug-ins that are installed in the default location. From this list, the specific plug-ins can be enabled:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh --plugins<span class="o">=</span><span class="s2">"ant,maven,shellcheck,xml"</span> <other options>
+
+<pre><code class="bash">$ test-patch.sh --plugins="ant,maven,shellcheck,xml" <other options>
</code></pre>
-<p>As a short-cut, every plug-in may be enabled via the special ‘all’ type:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh --plugins<span class="o">=</span><span class="s2">"all"</span> <other options>
+<p>As a short-cut, every plug-in may be enabled via the special 'all' type:</p>
+
+<pre><code class="bash">$ test-patch.sh --plugins="all" <other options>
</code></pre>
-<p><code>--plugins</code> also allows some basic “arithmetic”:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh --plugins<span class="o">=</span><span class="s2">"all,-checkstyle,-findbugs"</span> <other options>
+<p><code>--plugins</code> also allows some basic <q>arithmetic</q>:</p>
+
+<pre><code class="bash">$ test-patch.sh --plugins="all,-checkstyle,-findbugs" <other options>
</code></pre>
<p>This will enable all plug-ins for potential usage, except for checkstyle and findbugs.</p>
<p><strong>NOTE: The examples in this section will assume that the necessary <code>--plugins</code> option has been set on the command line as appropriate for your particular installation.</strong></p>
-<p>This command will execute basic patch testing against a patch file stored in “filename”:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">cd</span> <your repo>
-<span class="gp">$ </span><span class="nb">test</span>-patch.sh --dirty-workspace --project<span class="o">=</span>projectname <filename>
+<p>This command will execute basic patch testing against a patch file stored in <q>filename</q>:</p>
+
+<pre><code class="bash">$ cd <your repo>
+$ test-patch.sh --dirty-workspace --project=projectname <filename>
</code></pre>
<p>The <code>--dirty-workspace</code> flag tells test-patch that the repository is not clean and it is ok to continue. By default, unit tests are not run since they may take a significant amount of time.</p>
-<p>To do turn them on, we need to provide the –run-tests option:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">cd</span> <your repo>
-<span class="gp">$ </span><span class="nb">test</span>-patch.sh --dirty-workspace --run-tests <filename>
+<p>To do turn them on, we need to provide the --run-tests option:</p>
+
+<pre><code class="bash">$ cd <your repo>
+$ test-patch.sh --dirty-workspace --run-tests <filename>
</code></pre>
<p>This is the same command, but now runs the unit tests.</p>
<p>A typical configuration is to have two repositories. One with the code you are working on and another, clean repository. This means you can:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">cd</span> <workrepo>
-<span class="gp">$ </span>git diff master > /tmp/patchfile
-<span class="gp">$ </span><span class="nb">cd</span> ../<testrepo>
-<span class="gp">$ </span><span class="nb">test</span>-patch.sh --basedir<span class="o">=</span><testrepo> --resetrepo /tmp/patchfile
+
+<pre><code class="bash">$ cd <workrepo>
+$ git diff master > /tmp/patchfile
+$ cd ../<testrepo>
+$ test-patch.sh --basedir=<testrepo> --resetrepo /tmp/patchfile
</code></pre>
-<p>We used two new options here. –basedir sets the location of the repository to use for testing. –resetrepo tells test patch that it can go into <strong>destructive</strong> mode. Destructive mode will wipe out any changes made to that repository, so use it with care!</p>
+<p>We used two new options here. --basedir sets the location of the repository to use for testing. --resetrepo tells test patch that it can go into <strong>destructive</strong> mode. Destructive mode will wipe out any changes made to that repository, so use it with care!</p>
<p>After the tests have run, there is a directory that contains all of the test-patch related artifacts. This is generally referred to as the patchprocess directory. By default, test-patch tries to make something off of /tmp to contain this content. Using the <code>--patch-dir</code> option, one can specify exactly which directory to use. This is helpful for automated precommit testing so that Jenkins or other automated workflow system knows where to look to gather up the output.</p>
<p>For example:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh --jenkins --patch-dir<span class="o">=</span><span class="k">${</span><span class="nv">WORKSPACE</span><span class="k">}</span>/patchprocess --basedir<span class="o">=</span><span class="k">${</span><span class="nv">WORKSPACE</span><span class="k">}</span>/source <span class="k">${</span><span class="nv">WORKSPACE</span><span class="k">}</span>/patchfile
+
+<pre><code class="bash">$ test-patch.sh --jenkins --patch-dir=${WORKSPACE}/patchprocess --basedir=${WORKSPACE}/source ${WORKSPACE}/patchfile
</code></pre>
-<p>… will trigger test-patch to run in fully automated Jenkins mode, using ${WORKSPACE}/patchprocess as its scratch space, ${WORKSPACE}/source as the source repository, and ${WORKSPACE}/patchfile as the name of the patch to test against.</p>
+<p>... will trigger test-patch to run in fully automated Jenkins mode, using ${WORKSPACE}/patchprocess as its scratch space, ${WORKSPACE}/source as the source repository, and ${WORKSPACE}/patchfile as the name of the patch to test against.</p>
-<h1 id="build-tool">Build Tool</h1>
+<h1>Build Tool</h1>
<p>Out of the box, test-patch is built to use maven. But what if the project is built using something else, such as ant?</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh <span class="o">(</span>other options<span class="o">)</span> --build-tool<span class="o">=</span>ant
+
+<pre><code class="bash">$ test-patch.sh (other options) --build-tool=ant
</code></pre>
<p>will tell test-patch to use ant instead of maven to drive the project.</p>
-<h1 id="providing-patch-files">Providing Patch Files</h1>
+<h1>Providing Patch Files</h1>
-<h2 id="jira">JIRA</h2>
+<h2>JIRA</h2>
-<p>It is a fairly common practice within the Apache community to use Apache’s JIRA instance to store potential patches. As a result, test-patch supports providing just a JIRA issue number. test-patch will find the <em>last</em> attachment, download it, then process it.</p>
+<p>It is a fairly common practice within the Apache community to use Apache's JIRA instance to store potential patches. As a result, test-patch supports providing just a JIRA issue number. test-patch will find the <em>last</em> attachment, download it, then process it.</p>
<p>For example:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh <span class="o">(</span>other options<span class="o">)</span> HADOOP-9905
+
+<pre><code class="bash">$ test-patch.sh (other options) HADOOP-9905
</code></pre>
-<p>… will process the patch file associated with this JIRA issue.</p>
+<p>... will process the patch file associated with this JIRA issue.</p>
<p>If the Apache JIRA system is not in use, then override options may be provided on the command line to point to a different JIRA instance.</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh --jira-issue-re<span class="o">=</span><span class="s1">'^PROJECT-[0-9]+$'</span> --jira-base-url<span class="o">=</span><span class="s1">'https://example.com/jira'</span> PROJECT-90
+
+<pre><code class="bash">$ test-patch.sh --jira-issue-re='^PROJECT-[0-9]+$' --jira-base-url='https://example.com/jira' PROJECT-90
</code></pre>
-<p>… will process the patch file attached to PROJECT-90 on the JIRA instance located on the example.com server.</p>
+<p>... will process the patch file attached to PROJECT-90 on the JIRA instance located on the example.com server.</p>
-<h2 id="github">GITHUB</h2>
+<h2>GITHUB</h2>
<p>test-patch has some basic support for Github. test-patch supports many forms of providing pull requests to work on:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh --github-repo<span class="o">=</span>apache/pig 99
+
+<pre><code class="bash">$ test-patch.sh --github-repo=apache/pig 99
</code></pre>
<p>or</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh https://github.com/apache/pig/pulls/99
+
+<pre><code class="bash">$ test-patch.sh https://github.com/apache/pig/pulls/99
</code></pre>
<p>or</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh https://github.com/apache/pig/pulls/99.patch
+
+<pre><code class="bash">$ test-patch.sh https://github.com/apache/pig/pulls/99.patch
</code></pre>
-<p>… will process PR #99 on the apache/pig repo.</p>
+<p>... will process PR #99 on the apache/pig repo.</p>
-<h2 id="generic-urls">Generic URLs</h2>
+<h2>Generic URLs</h2>
<p>Luckily, test-patch supports provide ways to provide unified diffs via URLs.</p>
<p>For example:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh <span class="o">(</span>other options<span class="o">)</span> https://example.com/webserver/file.patch
+
+<pre><code class="bash">$ test-patch.sh (other options) https://example.com/webserver/file.patch
</code></pre>
-<p>… will download and process the file.patch from the example.com webserver.</p>
+<p>... will download and process the file.patch from the example.com webserver.</p>
-<h1 id="project-specific-capabilities">Project-specific Capabilities</h1>
+<h1>Project-specific Capabilities</h1>
<p>Due to the extensible nature of the system, test-patch allows for projects to define project-specific rules which we call personalities. (How to build those rules is covered elsewhere.) There are two ways to specify which personality to use:</p>
-<h2 id="direct-method">Direct Method</h2>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh <span class="o">(</span>other options<span class="o">)</span> --personality<span class="o">=(</span>filename<span class="o">)</span>
+<h2>Direct Method</h2>
+
+<pre><code class="bash">$ test-patch.sh (other options) --personality=(filename)
</code></pre>
<p>This tells test-patch to use the personality in the given file.</p>
-<h2 id="project-method">Project Method</h2>
+<h2>Project Method</h2>
+
+<p>However, test-patch can detect if it is a personality that is in its <q>personality</q> directory based upon the project name:</p>
-<p>However, test-patch can detect if it is a personality that is in its “personality” directory based upon the project name:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh <span class="o">(</span>other options<span class="o">)</span> --project<span class="o">=(</span>project<span class="o">)</span>
+<pre><code class="bash">$ test-patch.sh (other options) --project=(project)
</code></pre>
-<h1 id="multijdk">MultiJDK</h1>
+<h1>MultiJDK</h1>
-<p>For many projects, it is useful to test Java code against multiple versions of JDKs at the same time. test-patch can do this with the –multijdkdirs option:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh <span class="o">(</span>other options<span class="o">)</span> --multijdkdirs<span class="o">=</span><span class="s2">"/j/d/k/1,/j/d/k/2"</span>
+<p>For many projects, it is useful to test Java code against multiple versions of JDKs at the same time. test-patch can do this with the --multijdkdirs option:</p>
+
+<pre><code class="bash">$ test-patch.sh (other options) --multijdkdirs="/j/d/k/1,/j/d/k/2"
</code></pre>
-<p>Not all Java tests support this mode, but those that do will now run their tests with all of the given versions of Java consecutively (e.g., javac–the Java compliation test). Tests that do not support MultiJDK mode (e.g., checkstyle, mvn install) will use JAVA_HOME.</p>
+<p>Not all Java tests support this mode, but those that do will now run their tests with all of the given versions of Java consecutively (e.g., javac--the Java compliation test). Tests that do not support MultiJDK mode (e.g., checkstyle, mvn install) will use JAVA_HOME.</p>
<p>NOTE: JAVA_HOME is always appended to the list of JDKs in MultiJDK mode. If JAVA_HOME is in the list, it will be moved to the end.</p>
-<h1 id="docker">Docker</h1>
+<h1>Docker</h1>
<p>test-patch also has a mode to utilize Docker:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh <span class="o">(</span>other options<span class="o">)</span> --docker
+
+<pre><code class="bash">$ test-patch.sh (other options) --docker
</code></pre>
<p>This will do some preliminary setup and then re-execute itself inside a Docker container. For more information on how to provide a custom Dockerfile, see the advanced guide.</p>
-<h2 id="in-closing">In Closing</h2>
+<h2>In Closing</h2>
-<p>test-patch has many other features and command line options for the basic user. Many of these are self-explanatory. To see the list of options, run test-patch.sh without any options or with –help.</p>
+<p>test-patch has many other features and command line options for the basic user. Many of these are self-explanatory. To see the list of options, run test-patch.sh without any options or with --help.</p>
</div>
<div class="container">
@@ -344,7 +363,7 @@ as a whole.</p>
<div class="row-fluid">
<div class="span12 text-left">
<div class="span12">
- Copyright 2008-2015 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
+ Copyright 2008-2016 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
</div>
</div>
http://git-wip-us.apache.org/repos/asf/yetus/blob/d709aeb5/documentation/0.1.0/precommit-bugsystems/index.html
----------------------------------------------------------------------
diff --git a/documentation/0.1.0/precommit-bugsystems/index.html b/documentation/0.1.0/precommit-bugsystems/index.html
index bb6c6a6..6fbf025 100644
--- a/documentation/0.1.0/precommit-bugsystems/index.html
+++ b/documentation/0.1.0/precommit-bugsystems/index.html
@@ -118,10 +118,11 @@
under the License.
-->
-<h1 id="bug-system-support">Bug System Support</h1>
+<h1>Bug System Support</h1>
<p>test-patch has the ability to support multiple bug systems. Bug tools have some extra hooks to fetch patches, line-level reporting, and posting a final report. Every bug system plug-in must have one line in order to be recognized:</p>
-<pre class="highlight shell"><code>add_bugsystem <pluginname>
+
+<pre><code class="bash">add_bugsystem <pluginname>
</code></pre>
<ul>
@@ -143,7 +144,7 @@
<li><p>pluginname_write_comment</p>
<ul>
-<li>Given text input, write this output to the bug system as a comment. NOTE: It is the bug system’s responsibility to format appropriately.</li>
+<li>Given text input, write this output to the bug system as a comment. NOTE: It is the bug system's responsibility to format appropriately.</li>
</ul></li>
<li><p>pluginname_linecomments</p>
@@ -157,23 +158,24 @@
</ul></li>
</ul>
-<h1 id="bugzilla-specific">Bugzilla Specific</h1>
+<h1>Bugzilla Specific</h1>
+
+<p>Currently, Bugzilla support is read-only. To use it, the Bug ID must be preferenced with 'BZ:'. For example:</p>
-<p>Currently, Bugzilla support is read-only. To use it, the Bug ID must be preferenced with ‘BZ:’. For example:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh <span class="o">(</span>other options<span class="o">)</span> BZ:4
+<pre><code class="bash">$ test-patch.sh (other options) BZ:4
</code></pre>
-<p>… will pull down Bugzilla ID #4.</p>
+<p>... will pull down Bugzilla ID #4.</p>
-<p>Using the <code>--bugzilla-base-url</code> on the command line or BUGZILLA_BASE_URL in a project’s personality will define the location of the Bugzilla instance. By default, it is <a href="https://bz.apache.org/bugzilla">https://bz.apache.org/bugzilla</a> .</p>
+<p>Using the <code>--bugzilla-base-url</code> on the command line or BUGZILLA_BASE_URL in a project's personality will define the location of the Bugzilla instance. By default, it is <a href="https://bz.apache.org/bugzilla">https://bz.apache.org/bugzilla</a> .</p>
-<h1 id="github-specific">GitHub Specific</h1>
+<h1>GitHub Specific</h1>
<p>GitHub supports the full range of functionality, including putting comments on individual lines. Be aware, however, that test-patch.sh will require that GitHub PRs be fully rebased (i.e., a single commit) in many circumstances.</p>
<p>By default, the GitHub plug-in assumes that <a href="https://github.com">https://github.com</a> is the base URL for GitHub. Enterprise users may override this with the <code>--github-base-url</code> for the normal web user interface and <code>--github-api-url</code> for the API URL. Personalities may use GITHUB_API_URL and GITHUB_BASE_URL.</p>
-<p>The specific repository on GitHub is defined with either <code>--github-repo</code> on the command line or GITHUB_REPO in a personality. It should take the form of “user/repo”.</p>
+<p>The specific repository on GitHub is defined with either <code>--github-repo</code> on the command line or GITHUB_REPO in a personality. It should take the form of <q>user/repo</q>.</p>
<p>In order to comment on issues or, depending upon the security setup of the repo, authentication credentials. The GitHub plug-in supports two types:</p>
@@ -184,7 +186,7 @@
<p>Pull requests that are made off of a specific branch will switch the test repo to that branch, if permitted. If the pull request references a JIRA issue that matches the given JIRA issue regexp in the Subject, the JIRA plug-in will also be invoked as needed.</p>
-<h1 id="jira-specific">JIRA Specific</h1>
+<h1>JIRA Specific</h1>
<p>JIRA support allows both patch downloads and summary writes. It also supports branch detection-based upon the name of the attached patch file.</p>
@@ -199,7 +201,7 @@
<div class="row-fluid">
<div class="span12 text-left">
<div class="span12">
- Copyright 2008-2015 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
+ Copyright 2008-2016 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
</div>
</div>
http://git-wip-us.apache.org/repos/asf/yetus/blob/d709aeb5/documentation/0.1.0/precommit-buildtools/index.html
----------------------------------------------------------------------
diff --git a/documentation/0.1.0/precommit-buildtools/index.html b/documentation/0.1.0/precommit-buildtools/index.html
index ada21e3..faeb2a0 100644
--- a/documentation/0.1.0/precommit-buildtools/index.html
+++ b/documentation/0.1.0/precommit-buildtools/index.html
@@ -118,13 +118,14 @@
under the License.
-->
-<h1 id="build-tool-support">Build Tool Support</h1>
+<h1>Build Tool Support</h1>
<p>test-patch has the ability to support multiple build tools. Build tool plug-ins have some extra hooks to do source and object maintenance at key points. Every build tool plug-in must have one line in order to be recognized:</p>
-<pre class="highlight shell"><code>add_build_tool <pluginname>
+
+<pre><code class="bash">add_build_tool <pluginname>
</code></pre>
-<h1 id="global-variables">Global Variables</h1>
+<h1>Global Variables</h1>
<ul>
<li><p>BUILDTOOLCWD</p>
@@ -141,7 +142,7 @@
<p>For example, the gradle build tool does not have a standard way to execute checkstyle. So when checkstyle is requested, gradle_modules_worker sets UNSUPPORTED_TEST to true and returns out of the routine.</p>
-<h1 id="required-functions">Required Functions</h1>
+<h1>Required Functions</h1>
<ul>
<li><p>pluginname_buildfile</p>
@@ -157,7 +158,7 @@
<li><p>pluginname_modules_worker</p>
<ul>
-<li>Input is the branch and the test being run. This should call <code>modules_workers</code> with the generic parts to run that test on the build system. For example, if it is convention to use ‘test’ to trigger 'unit’ tests, then <code>module_workers</code> should be called with 'test’ appended onto its normal parameters.</li>
+<li>Input is the branch and the test being run. This should call <code>modules_workers</code> with the generic parts to run that test on the build system. For example, if it is convention to use 'test' to trigger 'unit' tests, then <code>module_workers</code> should be called with 'test' appended onto its normal parameters.</li>
</ul></li>
<li><p>pluginname_builtin_personality_modules</p>
@@ -171,7 +172,7 @@
</ul></li>
</ul>
-<h1 id="optional-functions">Optional Functions</h1>
+<h1>Optional Functions</h1>
<ul>
<li><p>pluginname_postapply_install</p>
@@ -203,29 +204,29 @@
<p><strong>WARNING</strong>: Be aware that directories that do not exist MAY be created by root by Docker itself under certain conditions. It is HIGHLY recommend that <code>pluginname_initialize</code> be used to create the necessary directories prior to be used in the <code>docker run</code> command.</p></li>
</ul>
-<h1 id="ant-specific">Ant Specific</h1>
+<h1>Ant Specific</h1>
-<h2 id="command-arguments">Command Arguments</h2>
+<h2>Command Arguments</h2>
<p>test-patch always passes -noinput to Ant. This forces ant to be non-interactive.</p>
-<h2 id="docker-mode">Docker Mode</h2>
+<h2>Docker Mode</h2>
<p>In Docker mode, the <code>${HOME}/.ivy2</code> directory is shared amongst all invocations.</p>
-<h1 id="gradle-specific">Gradle Specific</h1>
+<h1>Gradle Specific</h1>
<p>The gradle plug-in always rebuilds the gradlew file and uses gradlew as the method to execute commands.</p>
<p>In Docker mode, the <code>${HOME}/.gradle</code> directory is shared amongst all invocations.</p>
-<h1 id="maven-specific">Maven Specific</h1>
+<h1>Maven Specific</h1>
-<h2 id="command-arguments">Command Arguments</h2>
+<h2>Command Arguments</h2>
-<p>test-patch always passes –batch-mode to maven to force it into non-interactive mode. Additionally, some tests will also force -fae in order to get all of messages/errors during that mode. Some tests are executed with -DskipTests. Additional arguments should be handled via the personality.</p>
+<p>test-patch always passes --batch-mode to maven to force it into non-interactive mode. Additionally, some tests will also force -fae in order to get all of messages/errors during that mode. Some tests are executed with -DskipTests. Additional arguments should be handled via the personality.</p>
-<h2 id="per-instance-repositories">Per-instance Repositories</h2>
+<h2>Per-instance Repositories</h2>
<p>Under many common configurations, maven (as of 3.3.3 and lower) may not properly handle being executed by multiple processes simultaneously, especially given that some tests require the <code>mvn install</code> command to be used.</p>
@@ -235,15 +236,15 @@
<p>The location of the <code>settings.xml</code> may be changed via the <code>--mvn-settings</code> option.</p>
-<h2 id="docker-mode">Docker Mode</h2>
+<h2>Docker Mode</h2>
<p>In Docker mode, <code>${HOME}/.m2</code> is shared amongst all invocations. If <code>--mvn-custom-repos</code> is used, all of <code>--mvn-custom-repos-dir</code> is shared with all invocations. The per-instance directory will be calculated and configured after Docker has launched.</p>
-<h2 id="test-profile">Test Profile</h2>
+<h2>Test Profile</h2>
<p>By default, test-patch will pass -Ptest-patch to Maven. This will allow you to configure special actions that should only happen when running underneath test-patch.</p>
-<h2 id="custom-maven-tests">Custom Maven Tests</h2>
+<h2>Custom Maven Tests</h2>
<ul>
<li>Maven will trigger a maven install as part of the precompile.</li>
@@ -258,7 +259,7 @@
<div class="row-fluid">
<div class="span12 text-left">
<div class="span12">
- Copyright 2008-2015 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
+ Copyright 2008-2016 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
</div>
</div>
http://git-wip-us.apache.org/repos/asf/yetus/blob/d709aeb5/documentation/0.1.0/precommit-glossary/index.html
----------------------------------------------------------------------
diff --git a/documentation/0.1.0/precommit-glossary/index.html b/documentation/0.1.0/precommit-glossary/index.html
index 1b914e6..195c939 100644
--- a/documentation/0.1.0/precommit-glossary/index.html
+++ b/documentation/0.1.0/precommit-glossary/index.html
@@ -118,25 +118,25 @@
under the License.
-->
-<h1 id="glossary">Glossary</h1>
+<h1>Glossary</h1>
-<h2 id="generic-outside-definitions">Generic/outside definitions:</h2>
+<h2>Generic/outside definitions:</h2>
-<p>Apache’s <a href="https://community.apache.org/contributors/">new contributor documentation</a> and Maven’s <a href="https://maven.apache.org/glossary.html">glossary</a> are great places to start if you are new to Apache or Maven.</p>
+<p>Apache's <a href="https://community.apache.org/contributors/">new contributor documentation</a> and Maven's <a href="https://maven.apache.org/glossary.html">glossary</a> are great places to start if you are new to Apache or Maven.</p>
<ul>
<li>Module</li>
</ul>
-<p>Almost the same meaning as “sub-project” on Maven.</p>
+<p>Almost the same meaning as <q>sub-project</q> on Maven.</p>
-<h2 id="test-patch-specific">test-patch specific</h2>
+<h2>test-patch specific</h2>
<ul>
<li>Personality</li>
</ul>
-<p>A chunk of shell code that tells test-patch this particular project’s needs and special requirements</p>
+<p>A chunk of shell code that tells test-patch this particular project's needs and special requirements</p>
<ul>
<li>Plug-ins</li>
@@ -148,7 +148,7 @@
<li>Precommit</li>
</ul>
-<p>An automated process that verifies a patch is “good” prior to a committer looking at it.</p>
+<p>An automated process that verifies a patch is <q>good</q> prior to a committer looking at it.</p>
</div>
<div class="container">
@@ -157,7 +157,7 @@
<div class="row-fluid">
<div class="span12 text-left">
<div class="span12">
- Copyright 2008-2015 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
+ Copyright 2008-2016 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
</div>
</div>
http://git-wip-us.apache.org/repos/asf/yetus/blob/d709aeb5/documentation/0.1.0/precommit-patchnames/index.html
----------------------------------------------------------------------
diff --git a/documentation/0.1.0/precommit-patchnames/index.html b/documentation/0.1.0/precommit-patchnames/index.html
index 7adff7f..6db1433 100644
--- a/documentation/0.1.0/precommit-patchnames/index.html
+++ b/documentation/0.1.0/precommit-patchnames/index.html
@@ -124,7 +124,7 @@ procedures for patch file names:</p>
<p>JIRA:</p>
<p>If JIRA support is configured, attach the patch to the given ISSUE and
-click ‘Submit Patch’. The patch file should be named one of:</p>
+click 'Submit Patch'. The patch file should be named one of:</p>
<ul>
<li>ISSUE.patch</li>
@@ -135,7 +135,7 @@ click ‘Submit Patch’. The patch file should be named one of:</p>
<li>ISSUE-branch.##.patch</li>
</ul>
-<p>If Github support is also configured, a comment that contains a link to a Pull Request’s
+<p>If Github support is also configured, a comment that contains a link to a Pull Request's
patch file (e.g., <a href="https://github.com/user/repo/pull/1.patch">https://github.com/user/repo/pull/1.patch</a>) will pull the patch from
the given Github PR.</p>
@@ -146,7 +146,7 @@ the given Github PR.</p>
<div class="row-fluid">
<div class="span12 text-left">
<div class="span12">
- Copyright 2008-2015 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
+ Copyright 2008-2016 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
</div>
</div>
http://git-wip-us.apache.org/repos/asf/yetus/blob/d709aeb5/documentation/0.1.0/precommit-smart-apply-patch/index.html
----------------------------------------------------------------------
diff --git a/documentation/0.1.0/precommit-smart-apply-patch/index.html b/documentation/0.1.0/precommit-smart-apply-patch/index.html
index f5b2159..6f91ae3 100644
--- a/documentation/0.1.0/precommit-smart-apply-patch/index.html
+++ b/documentation/0.1.0/precommit-smart-apply-patch/index.html
@@ -118,24 +118,27 @@
under the License.
-->
-<h1 id="smart-apply-patch">smart-apply-patch</h1>
+<h1>smart-apply-patch</h1>
<p><code>smart-apply-patch</code> is a command to help apply patches easily. It uses the same plug-ins and many of the same options as test-patch. This means that it can, for example, fetch patches from JIRA and apply them to a local source tree.</p>
-<h1 id="usage">Usage</h1>
+<h1>Usage</h1>
<p>Its simpliest form is used when a patch is stored in a local file:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span>smart-apply-patch patch
+
+<pre><code class="bash">$ smart-apply-patch patch
</code></pre>
<p>This will cause the command to run through various ways to verify and then apply the patch to the current repo, including deducing a patch level.</p>
<p>Perhaps you just want to see if the patch even applies without changing your local repo. The <code>--dry-run</code> option will just test for applicability:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span>smart-apply-patch --dry-run patch
+
+<pre><code class="bash">$ smart-apply-patch --dry-run patch
</code></pre>
<p>For committers of projects, there is a special mode:</p>
-<pre class="highlight shell"><code><span class="gp">$ </span>smart-apply-patch --committer patch
+
+<pre><code class="bash">$ smart-apply-patch --committer patch
</code></pre>
<p>that in addition to applying the patch will also attempt to:</p>
@@ -153,7 +156,7 @@
<div class="row-fluid">
<div class="span12 text-left">
<div class="span12">
- Copyright 2008-2015 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
+ Copyright 2008-2016 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
</div>
</div>
http://git-wip-us.apache.org/repos/asf/yetus/blob/d709aeb5/documentation/0.1.0/precommit-testformats/index.html
----------------------------------------------------------------------
diff --git a/documentation/0.1.0/precommit-testformats/index.html b/documentation/0.1.0/precommit-testformats/index.html
index a27489b..1b3cd83 100644
--- a/documentation/0.1.0/precommit-testformats/index.html
+++ b/documentation/0.1.0/precommit-testformats/index.html
@@ -118,10 +118,11 @@
under the License.
-->
-<h1 id="test-format-support">Test Format Support</h1>
+<h1>Test Format Support</h1>
<p>test-patch has the ability to support multiple test formats. Test formats have some extra hooks to process the output of test tools and write the results to some tables. Every test format plug-in must have one line in order to be recognized:</p>
-<pre class="highlight shell"><code>add_test_format <pluginname>
+
+<pre><code class="bash">add_test_format <pluginname>
</code></pre>
<ul>
@@ -144,7 +145,7 @@
<div class="row-fluid">
<div class="span12 text-left">
<div class="span12">
- Copyright 2008-2015 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
+ Copyright 2008-2016 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. Apache Yetus and the Apache feather logo are trademarks of The Apache Software Foundation.
</div>
</div>