yetus-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From a.@apache.org
Subject [1/9] yetus git commit: git hash 2113cfa875876f25a48006786b4783605acc8ea3
Date Fri, 16 Jun 2017 14:20:04 GMT
Repository: yetus
Updated Branches:
  refs/heads/asf-site 07cb76b7d -> 012f133c0


http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/audience-annotations-apidocs/overview-summary.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/audience-annotations-apidocs/overview-summary.html b/documentation/in-progress/audience-annotations-apidocs/overview-summary.html
index be4be72..eb60d71 100644
--- a/documentation/in-progress/audience-annotations-apidocs/overview-summary.html
+++ b/documentation/in-progress/audience-annotations-apidocs/overview-summary.html
@@ -2,10 +2,10 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_111) on Thu Jun 01 09:34:58 PDT 2017 -->
+<!-- Generated by javadoc (1.8.0_92) on Fri Jun 16 07:11:23 PDT 2017 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Overview (Apache Yetus - Audience Annotations Component 0.5.0-SNAPSHOT API)</title>
-<meta name="date" content="2017-06-01">
+<meta name="date" content="2017-06-16">
 <link rel="stylesheet" type="text/css" href="stylesheet.css" title="Style">
 <script type="text/javascript" src="script.js"></script>
 </head>

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/audience-annotations-apidocs/overview-tree.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/audience-annotations-apidocs/overview-tree.html b/documentation/in-progress/audience-annotations-apidocs/overview-tree.html
index 9eedc89..bd0b173 100644
--- a/documentation/in-progress/audience-annotations-apidocs/overview-tree.html
+++ b/documentation/in-progress/audience-annotations-apidocs/overview-tree.html
@@ -2,10 +2,10 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_111) on Thu Jun 01 09:34:58 PDT 2017 -->
+<!-- Generated by javadoc (1.8.0_92) on Fri Jun 16 07:11:23 PDT 2017 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Class Hierarchy (Apache Yetus - Audience Annotations Component 0.5.0-SNAPSHOT API)</title>
-<meta name="date" content="2017-06-01">
+<meta name="date" content="2017-06-16">
 <link rel="stylesheet" type="text/css" href="stylesheet.css" title="Style">
 <script type="text/javascript" src="script.js"></script>
 </head>

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/audience-annotations-apidocs/stylesheet.css
----------------------------------------------------------------------
diff --git a/documentation/in-progress/audience-annotations-apidocs/stylesheet.css b/documentation/in-progress/audience-annotations-apidocs/stylesheet.css
index 0aeaa97..98055b2 100644
--- a/documentation/in-progress/audience-annotations-apidocs/stylesheet.css
+++ b/documentation/in-progress/audience-annotations-apidocs/stylesheet.css
@@ -2,16 +2,19 @@
 /*
 Overall document style
 */
+
+@import url('resources/fonts/dejavu.css');
+
 body {
     background-color:#ffffff;
     color:#353833;
-    font-family:Arial, Helvetica, sans-serif;
-    font-size:76%;
+    font-family:'DejaVu Sans', Arial, Helvetica, sans-serif;
+    font-size:14px;
     margin:0;
 }
 a:link, a:visited {
     text-decoration:none;
-    color:#4c6b87;
+    color:#4A6782;
 }
 a:hover, a:focus {
     text-decoration:none;
@@ -19,7 +22,7 @@ a:hover, a:focus {
 }
 a:active {
     text-decoration:none;
-    color:#4c6b87;
+    color:#4A6782;
 }
 a[name] {
     color:#353833;
@@ -29,41 +32,51 @@ a[name]:hover {
     color:#353833;
 }
 pre {
-    font-size:1.3em;
+    font-family:'DejaVu Sans Mono', monospace;
+    font-size:14px;
 }
 h1 {
-    font-size:1.8em;
+    font-size:20px;
 }
 h2 {
-    font-size:1.5em;
+    font-size:18px;
 }
 h3 {
-    font-size:1.4em;
+    font-size:16px;
+    font-style:italic;
 }
 h4 {
-    font-size:1.3em;
+    font-size:13px;
 }
 h5 {
-    font-size:1.2em;
+    font-size:12px;
 }
 h6 {
-    font-size:1.1em;
+    font-size:11px;
 }
 ul {
     list-style-type:disc;
 }
 code, tt {
-    font-size:1.2em;
+    font-family:'DejaVu Sans Mono', monospace;
+    font-size:14px;
+    padding-top:4px;
+    margin-top:8px;
+    line-height:1.4em;
 }
 dt code {
-    font-size:1.2em;
+    font-family:'DejaVu Sans Mono', monospace;
+    font-size:14px;
+    padding-top:4px;
 }
 table tr td dt code {
-    font-size:1.2em;
+    font-family:'DejaVu Sans Mono', monospace;
+    font-size:14px;
     vertical-align:top;
+    padding-top:4px;
 }
 sup {
-    font-size:.6em;
+    font-size:8px;
 }
 /*
 Document title and Copyright styles
@@ -76,9 +89,9 @@ Document title and Copyright styles
 .aboutLanguage {
     float:right;
     padding:0px 21px;
-    font-size:.8em;
+    font-size:11px;
     z-index:200;
-    margin-top:-7px;
+    margin-top:-9px;
 }
 .legalCopy {
     margin-left:.5em;
@@ -92,9 +105,6 @@ Document title and Copyright styles
 }
 .tab {
     background-color:#0066FF;
-    background-image:url(resources/titlebar.gif);
-    background-position:left top;
-    background-repeat:no-repeat;
     color:#ffffff;
     padding:8px;
     width:5em;
@@ -104,17 +114,15 @@ Document title and Copyright styles
 Navigation bar styles
 */
 .bar {
-    background-image:url(resources/background.gif);
-    background-repeat:repeat-x;
+    background-color:#4D7A97;
     color:#FFFFFF;
     padding:.8em .5em .4em .8em;
     height:auto;/*height:1.8em;*/
-    font-size:1em;
+    font-size:11px;
     margin:0;
 }
 .topNav {
-    background-image:url(resources/background.gif);
-    background-repeat:repeat-x;
+    background-color:#4D7A97;
     color:#FFFFFF;
     float:left;
     padding:0;
@@ -123,11 +131,11 @@ Navigation bar styles
     height:2.8em;
     padding-top:10px;
     overflow:hidden;
+    font-size:12px; 
 }
 .bottomNav {
     margin-top:10px;
-    background-image:url(resources/background.gif);
-    background-repeat:repeat-x;
+    background-color:#4D7A97;
     color:#FFFFFF;
     float:left;
     padding:0;
@@ -136,18 +144,20 @@ Navigation bar styles
     height:2.8em;
     padding-top:10px;
     overflow:hidden;
+    font-size:12px;
 }
 .subNav {
     background-color:#dee3e9;
-    border-bottom:1px solid #9eadc0;
     float:left;
     width:100%;
     overflow:hidden;
+    font-size:12px;
 }
 .subNav div {
     clear:left;
     float:left;
     padding:0 0 5px 6px;
+    text-transform:uppercase;
 }
 ul.navList, ul.subNavList {
     float:left;
@@ -157,27 +167,33 @@ ul.navList, ul.subNavList {
 ul.navList li{
     list-style:none;
     float:left;
-    padding:3px 6px;
+    padding: 5px 6px;
+    text-transform:uppercase;
 }
 ul.subNavList li{
     list-style:none;
     float:left;
-    font-size:90%;
 }
 .topNav a:link, .topNav a:active, .topNav a:visited, .bottomNav a:link, .bottomNav a:active, .bottomNav a:visited {
     color:#FFFFFF;
     text-decoration:none;
+    text-transform:uppercase;
 }
 .topNav a:hover, .bottomNav a:hover {
     text-decoration:none;
     color:#bb7a2a;
+    text-transform:uppercase;
 }
 .navBarCell1Rev {
-    background-image:url(resources/tab.gif);
-    background-color:#a88834;
-    color:#FFFFFF;
+    background-color:#F8981D;
+    color:#253441;
     margin: auto 5px;
-    border:1px solid #c9aa44;
+}
+.skipNav {
+    position:absolute;
+    top:auto;
+    left:-9999px;
+    overflow:hidden;
 }
 /*
 Page header and footer styles
@@ -191,8 +207,11 @@ Page header and footer styles
     margin:10px;
     position:relative;
 }
+.indexHeader span{
+    margin-right:15px;
+}
 .indexHeader h1 {
-    font-size:1.3em;
+    font-size:13px;
 }
 .title {
     color:#2c4557;
@@ -202,7 +221,7 @@ Page header and footer styles
     margin:5px 0 0 0;
 }
 .header ul {
-    margin:0 0 25px 0;
+    margin:0 0 15px 0;
     padding:0;
 }
 .footer ul {
@@ -210,24 +229,22 @@ Page header and footer styles
 }
 .header ul li, .footer ul li {
     list-style:none;
-    font-size:1.2em;
+    font-size:13px;
 }
 /*
 Heading styles
 */
 div.details ul.blockList ul.blockList ul.blockList li.blockList h4, div.details ul.blockList ul.blockList ul.blockListLast li.blockList h4 {
     background-color:#dee3e9;
-    border-top:1px solid #9eadc0;
-    border-bottom:1px solid #9eadc0;
+    border:1px solid #d0d9e0;
     margin:0 0 6px -8px;
-    padding:2px 5px;
+    padding:7px 5px;
 }
 ul.blockList ul.blockList ul.blockList li.blockList h3 {
     background-color:#dee3e9;
-    border-top:1px solid #9eadc0;
-    border-bottom:1px solid #9eadc0;
+    border:1px solid #d0d9e0;
     margin:0 0 6px -8px;
-    padding:2px 5px;
+    padding:7px 5px;
 }
 ul.blockList ul.blockList li.blockList h3 {
     padding:0;
@@ -247,10 +264,10 @@ Page layout container styles
 .indexContainer {
     margin:10px;
     position:relative;
-    font-size:1.0em;
+    font-size:12px;
 }
 .indexContainer h2 {
-    font-size:1.1em;
+    font-size:13px;
     padding:0 0 3px 0;
 }
 .indexContainer ul {
@@ -259,15 +276,18 @@ Page layout container styles
 }
 .indexContainer ul li {
     list-style:none;
+    padding-top:2px;
 }
 .contentContainer .description dl dt, .contentContainer .details dl dt, .serializedFormContainer dl dt {
-    font-size:1.1em;
+    font-size:12px;
     font-weight:bold;
     margin:10px 0 0 0;
     color:#4E4E4E;
 }
 .contentContainer .description dl dd, .contentContainer .details dl dd, .serializedFormContainer dl dd {
-    margin:10px 0 10px 20px;
+    margin:5px 0 10px 0px;
+    font-size:14px;
+    font-family:'DejaVu Sans Mono',monospace;
 }
 .serializedFormContainer dl.nameValue dt {
     margin-left:1px;
@@ -306,25 +326,24 @@ ul.blockList, ul.blockListLast {
 }
 ul.blockList li.blockList, ul.blockListLast li.blockList {
     list-style:none;
-    margin-bottom:25px;
+    margin-bottom:15px;
+    line-height:1.4;
 }
 ul.blockList ul.blockList li.blockList, ul.blockList ul.blockListLast li.blockList {
     padding:0px 20px 5px 10px;
-    border:1px solid #9eadc0;
-    background-color:#f9f9f9;
+    border:1px solid #ededed; 
+    background-color:#f8f8f8;
 }
 ul.blockList ul.blockList ul.blockList li.blockList, ul.blockList ul.blockList ul.blockListLast li.blockList {
     padding:0 0 5px 8px;
     background-color:#ffffff;
-    border:1px solid #9eadc0;
-    border-top:none;
+    border:none;
 }
 ul.blockList ul.blockList ul.blockList ul.blockList li.blockList {
     margin-left:0;
     padding-left:0;
     padding-bottom:15px;
     border:none;
-    border-bottom:1px solid #9eadc0;
 }
 ul.blockList ul.blockList ul.blockList ul.blockList li.blockListLast {
     list-style:none;
@@ -338,107 +357,155 @@ table tr td dl, table tr td dl dt, table tr td dl dd {
 /*
 Table styles
 */
-.contentContainer table, .classUseContainer table, .constantValuesContainer table {
-    border-bottom:1px solid #9eadc0;
-    width:100%;
-}
-.contentContainer ul li table, .classUseContainer ul li table, .constantValuesContainer ul li table {
+.overviewSummary, .memberSummary, .typeSummary, .useSummary, .constantsSummary, .deprecatedSummary {
     width:100%;
+    border-left:1px solid #EEE; 
+    border-right:1px solid #EEE; 
+    border-bottom:1px solid #EEE; 
 }
-.contentContainer .description table, .contentContainer .details table {
-    border-bottom:none;
-}
-.contentContainer ul li table th.colOne, .contentContainer ul li table th.colFirst, .contentContainer ul li table th.colLast, .classUseContainer ul li table th, .constantValuesContainer ul li table th, .contentContainer ul li table td.colOne, .contentContainer ul li table td.colFirst, .contentContainer ul li table td.colLast, .classUseContainer ul li table td, .constantValuesContainer ul li table td{
-    vertical-align:top;
-    padding-right:20px;
-}
-.contentContainer ul li table th.colLast, .classUseContainer ul li table th.colLast,.constantValuesContainer ul li table th.colLast,
-.contentContainer ul li table td.colLast, .classUseContainer ul li table td.colLast,.constantValuesContainer ul li table td.colLast,
-.contentContainer ul li table th.colOne, .classUseContainer ul li table th.colOne,
-.contentContainer ul li table td.colOne, .classUseContainer ul li table td.colOne {
-    padding-right:3px;
+.overviewSummary, .memberSummary  {
+    padding:0px;
 }
-.overviewSummary caption, .packageSummary caption, .contentContainer ul.blockList li.blockList caption, .summary caption, .classUseContainer caption, .constantValuesContainer caption {
+.overviewSummary caption, .memberSummary caption, .typeSummary caption,
+.useSummary caption, .constantsSummary caption, .deprecatedSummary caption {
     position:relative;
     text-align:left;
     background-repeat:no-repeat;
-    color:#FFFFFF;
+    color:#253441;
     font-weight:bold;
     clear:none;
     overflow:hidden;
     padding:0px;
+    padding-top:10px;
+    padding-left:1px;
     margin:0px;
-}
-caption a:link, caption a:hover, caption a:active, caption a:visited {
+    white-space:pre;
+}
+.overviewSummary caption a:link, .memberSummary caption a:link, .typeSummary caption a:link,
+.useSummary caption a:link, .constantsSummary caption a:link, .deprecatedSummary caption a:link,
+.overviewSummary caption a:hover, .memberSummary caption a:hover, .typeSummary caption a:hover,
+.useSummary caption a:hover, .constantsSummary caption a:hover, .deprecatedSummary caption a:hover,
+.overviewSummary caption a:active, .memberSummary caption a:active, .typeSummary caption a:active,
+.useSummary caption a:active, .constantsSummary caption a:active, .deprecatedSummary caption a:active,
+.overviewSummary caption a:visited, .memberSummary caption a:visited, .typeSummary caption a:visited,
+.useSummary caption a:visited, .constantsSummary caption a:visited, .deprecatedSummary caption a:visited {
     color:#FFFFFF;
 }
-.overviewSummary caption span, .packageSummary caption span, .contentContainer ul.blockList li.blockList caption span, .summary caption span, .classUseContainer caption span, .constantValuesContainer caption span {
+.overviewSummary caption span, .memberSummary caption span, .typeSummary caption span,
+.useSummary caption span, .constantsSummary caption span, .deprecatedSummary caption span {
     white-space:nowrap;
-    padding-top:8px;
-    padding-left:8px;
-    display:block;
+    padding-top:5px;
+    padding-left:12px;
+    padding-right:12px;
+    padding-bottom:7px;
+    display:inline-block;
     float:left;
-    background-image:url(resources/titlebar.gif);
-    height:18px;
+    background-color:#F8981D;
+    border: none;
+    height:16px;
 }
-.overviewSummary .tabEnd, .packageSummary .tabEnd, .contentContainer ul.blockList li.blockList .tabEnd, .summary .tabEnd, .classUseContainer .tabEnd, .constantValuesContainer .tabEnd {
-    width:10px;
-    background-image:url(resources/titlebar_end.gif);
-    background-repeat:no-repeat;
-    background-position:top right;
-    position:relative;
+.memberSummary caption span.activeTableTab span {
+    white-space:nowrap;
+    padding-top:5px;
+    padding-left:12px;
+    padding-right:12px;
+    margin-right:3px;
+    display:inline-block;
     float:left;
+    background-color:#F8981D;
+    height:16px;
 }
-ul.blockList ul.blockList li.blockList table {
-    margin:0 0 12px 0px;
-    width:100%;
+.memberSummary caption span.tableTab span {
+    white-space:nowrap;
+    padding-top:5px;
+    padding-left:12px;
+    padding-right:12px;
+    margin-right:3px;
+    display:inline-block;
+    float:left;
+    background-color:#4D7A97;
+    height:16px;
+}
+.memberSummary caption span.tableTab, .memberSummary caption span.activeTableTab {
+    padding-top:0px;
+    padding-left:0px;
+    padding-right:0px;
+    background-image:none;
+    float:none;
+    display:inline;
 }
-.tableSubHeadingColor {
-    background-color: #EEEEFF;
+.overviewSummary .tabEnd, .memberSummary .tabEnd, .typeSummary .tabEnd,
+.useSummary .tabEnd, .constantsSummary .tabEnd, .deprecatedSummary .tabEnd {
+    display:none;
+    width:5px;
+    position:relative;
+    float:left;
+    background-color:#F8981D;
 }
-.altColor {
-    background-color:#eeeeef;
+.memberSummary .activeTableTab .tabEnd {
+    display:none;
+    width:5px;
+    margin-right:3px;
+    position:relative; 
+    float:left;
+    background-color:#F8981D;
 }
-.rowColor {
-    background-color:#ffffff;
+.memberSummary .tableTab .tabEnd {
+    display:none;
+    width:5px;
+    margin-right:3px;
+    position:relative;
+    background-color:#4D7A97;
+    float:left;
+
 }
-.overviewSummary td, .packageSummary td, .contentContainer ul.blockList li.blockList td, .summary td, .classUseContainer td, .constantValuesContainer td {
+.overviewSummary td, .memberSummary td, .typeSummary td,
+.useSummary td, .constantsSummary td, .deprecatedSummary td {
     text-align:left;
-    padding:3px 3px 3px 7px;
+    padding:0px 0px 12px 10px;
+}
+th.colOne, th.colFirst, th.colLast, .useSummary th, .constantsSummary th,
+td.colOne, td.colFirst, td.colLast, .useSummary td, .constantsSummary td{
+    vertical-align:top;
+    padding-right:0px;
+    padding-top:8px;
+    padding-bottom:3px;
 }
-th.colFirst, th.colLast, th.colOne, .constantValuesContainer th {
+th.colFirst, th.colLast, th.colOne, .constantsSummary th {
     background:#dee3e9;
-    border-top:1px solid #9eadc0;
-    border-bottom:1px solid #9eadc0;
     text-align:left;
-    padding:3px 3px 3px 7px;
-}
-td.colOne a:link, td.colOne a:active, td.colOne a:visited, td.colOne a:hover, td.colFirst a:link, td.colFirst a:active, td.colFirst a:visited, td.colFirst a:hover, td.colLast a:link, td.colLast a:active, td.colLast a:visited, td.colLast a:hover, .constantValuesContainer td a:link, .constantValuesContainer td a:active, .constantValuesContainer td a:visited, .constantValuesContainer td a:hover {
-    font-weight:bold;
+    padding:8px 3px 3px 7px;
 }
 td.colFirst, th.colFirst {
-    border-left:1px solid #9eadc0;
     white-space:nowrap;
+    font-size:13px;
 }
 td.colLast, th.colLast {
-    border-right:1px solid #9eadc0;
+    font-size:13px;
 }
 td.colOne, th.colOne {
-    border-right:1px solid #9eadc0;
-    border-left:1px solid #9eadc0;
+    font-size:13px;
+}
+.overviewSummary td.colFirst, .overviewSummary th.colFirst,
+.useSummary td.colFirst, .useSummary th.colFirst,
+.overviewSummary td.colOne, .overviewSummary th.colOne,
+.memberSummary td.colFirst, .memberSummary th.colFirst,
+.memberSummary td.colOne, .memberSummary th.colOne,
+.typeSummary td.colFirst{
+    width:25%;
+    vertical-align:top;
 }
-table.overviewSummary  {
-    padding:0px;
-    margin-left:0px;
+td.colOne a:link, td.colOne a:active, td.colOne a:visited, td.colOne a:hover, td.colFirst a:link, td.colFirst a:active, td.colFirst a:visited, td.colFirst a:hover, td.colLast a:link, td.colLast a:active, td.colLast a:visited, td.colLast a:hover, .constantValuesContainer td a:link, .constantValuesContainer td a:active, .constantValuesContainer td a:visited, .constantValuesContainer td a:hover {
+    font-weight:bold;
 }
-table.overviewSummary td.colFirst, table.overviewSummary th.colFirst,
-table.overviewSummary td.colOne, table.overviewSummary th.colOne {
-    width:25%;
-    vertical-align:middle;
+.tableSubHeadingColor {
+    background-color:#EEEEFF;
 }
-table.packageSummary td.colFirst, table.overviewSummary th.colFirst {
-    width:25%;
-    vertical-align:middle;
+.altColor {
+    background-color:#FFFFFF;
+}
+.rowColor {
+    background-color:#EEEEEF;
 }
 /*
 Content styles
@@ -453,6 +520,24 @@ Content styles
 .docSummary {
     padding:0;
 }
+
+ul.blockList ul.blockList ul.blockList li.blockList h3 {
+    font-style:normal;
+}
+
+div.block {
+    font-size:14px;
+    font-family:'DejaVu Serif', Georgia, "Times New Roman", Times, serif;
+}
+
+td.colLast div {
+    padding-top:0px;
+}
+
+
+td.colLast a {
+    padding-bottom:3px;
+}
 /*
 Formatting effect styles
 */
@@ -463,12 +548,27 @@ Formatting effect styles
 h1.hidden {
     visibility:hidden;
     overflow:hidden;
-    font-size:.9em;
+    font-size:10px;
 }
 .block {
     display:block;
-    margin:3px 0 0 0;
+    margin:3px 10px 2px 0px;
+    color:#474747;
 }
-.strong {
+.deprecatedLabel, .descfrmTypeLabel, .memberNameLabel, .memberNameLink,
+.overrideSpecifyLabel, .packageHierarchyLabel, .paramLabel, .returnLabel,
+.seeLabel, .simpleTagLabel, .throwsLabel, .typeNameLabel, .typeNameLink {
     font-weight:bold;
 }
+.deprecationComment, .emphasizedPhrase, .interfaceName {
+    font-style:italic;
+}
+
+div.block div.block span.deprecationComment, div.block div.block span.emphasizedPhrase,
+div.block div.block span.interfaceName {
+    font-style:normal;
+}
+
+div.contentContainer ul.blockList li.blockList h2{
+    padding-bottom:0px;
+}

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/index.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/index.html b/documentation/in-progress/index.html
index d72acf4..9b92d48 100644
--- a/documentation/in-progress/index.html
+++ b/documentation/in-progress/index.html
@@ -157,7 +157,6 @@ Options:
                         file to <span class="nb">read</span>
   --skipprnorep         Skip Private &amp; Not Replaceable
 </code></pre>
-
 <p>You can mark a file to be ignored by shelldocs by adding <q>SHELLDOC-IGNORE</q> as a comment in its own line.</p>
 
 <h1 id="yetus-audience-annotations">Yetus Audience Annotations</h1>

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/precommit-advanced/index.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/precommit-advanced/index.html b/documentation/in-progress/precommit-advanced/index.html
index a3f9989..379c413 100644
--- a/documentation/in-progress/precommit-advanced/index.html
+++ b/documentation/in-progress/precommit-advanced/index.html
@@ -147,7 +147,7 @@
 
 <p>The &lsquo;fail&rsquo; setting is always the last option that test-patch will use and may be omitted unless it is the only option.</p>
 
-<p>For example, <code>--dockeronfail=continue</code> means if the Dockerfile can&rsquo;t be found, just turn off Docker support and continue running.  <code>--dockeronfail=fallback</code> will switch to the bundled Dockerfile and then fail the build if docker fails to work. <code>--dockeronfail=fail</code> means to just fail the build and do not try any other mechanisms of recovery. The default is &#39;fallback,continue,fail&rsquo; which will allow test-patch to try to continue executing as much as it possibily can.</p>
+<p>For example, <code>--dockeronfail=continue</code> means if the Dockerfile can&rsquo;t be found, just turn off Docker support and continue running.  <code>--dockeronfail=fallback</code> will switch to the bundled Dockerfile and then fail the build if docker fails to work. <code>--dockeronfail=fail</code> means to just fail the build and do not try any other mechanisms of recovery. The default is &lsquo;fallback,continue,fail&rsquo; which will allow test-patch to try to continue executing as much as it possibily can.</p>
 
 <p>Be aware that if the Dockerfile is found and the docker command works, test-patch will always fail the build if the Dockerfile itself fails the build.  It will not attempt to continue in the non-Docker mode.</p>
 
@@ -161,20 +161,17 @@
 
 <h2 id="common-plug-in-functions">Common Plug-in Functions</h2>
 
-<p>Every plug-in must have one line in order to be recognized, usually an &#39;add&rsquo; statement.  Test plug-ins, for example, have this statement:</p>
+<p>Every plug-in must have one line in order to be recognized, usually an &lsquo;add&rsquo; statement.  Test plug-ins, for example, have this statement:</p>
 <pre class="highlight shell"><code>add_test_type &lt;pluginname&gt;
 </code></pre>
-
-<p>This function call registers the <code>pluginname</code> so that test-patch knows that it exists.  Plug-in names must be unique across all the different plug-in types.  Additionally, the &#39;all&rsquo; plug-in is reserved.  The <code>pluginname</code> also acts as the key to the custom functions that you can define. For example:</p>
+<p>This function call registers the <code>pluginname</code> so that test-patch knows that it exists.  Plug-in names must be unique across all the different plug-in types.  Additionally, the &lsquo;all&rsquo; plug-in is reserved.  The <code>pluginname</code> also acts as the key to the custom functions that you can define. For example:</p>
 <pre class="highlight shell"><code><span class="k">function </span>pluginname_filefilter
 </code></pre>
-
 <p>defines the filefilter for the <code>pluginname</code> plug-in.</p>
 
 <p>Similarly, there are other functions that may be defined during the test-patch run:</p>
 <pre class="highlight plaintext"><code>HINT: It is recommended to make the pluginname relatively small, 10 characters at the most.  Otherwise, the ASCII output table may be skewed.
 </code></pre>
-
 <ul>
 <li><p>pluginname_usage</p>
 
@@ -240,7 +237,6 @@
 <p>Plug-ins geared towards independent tests are registered via:</p>
 <pre class="highlight shell"><code>add_test_type &lt;pluginname&gt;
 </code></pre>
-
 <ul>
 <li><p>pluginname_filefilter</p>
 
@@ -295,7 +291,6 @@
   <span class="nv">GITHUB_REPO</span><span class="o">=</span><span class="s2">"apache/yetus"</span>
 <span class="o">}</span>
 </code></pre>
-
 <h2 id="test-determination">Test Determination</h2>
 
 <p>The <code>personality_file_tests</code> function determines which tests to turn on based upon the file name.  It is relatively simple.  For example, to turn on a full suite of tests for Java files:</p>
@@ -313,10 +308,9 @@
 
 <span class="o">}</span>
 </code></pre>
-
 <p>The <code>add_test</code> function is used to activate the standard tests.  Additional plug-ins (such as checkstyle), will get queried on their own.</p>
 
-<h2 id="module-amp-profile-determination">Module &amp; Profile Determination</h2>
+<h2 id="module-profile-determination">Module &amp; Profile Determination</h2>
 
 <p>Once the tests are determined, it is now time to pick which <a href="precommit-glossary.md#genericoutside-definitions">modules</a> should get used.  That&rsquo;s the job of the <code>personality_modules</code> function.</p>
 <pre class="highlight shell"><code><span class="k">function </span>personality_modules
@@ -330,7 +324,6 @@
 
 <span class="o">}</span>
 </code></pre>
-
 <p>It takes exactly two parameters <code>repostatus</code> and <code>testtype</code>.</p>
 
 <p>The <code>repostatus</code> parameter tells the <code>personality</code> function exactly what state the source repository is in.  It can only be in one of two states:  <code>branch</code> or <code>patch</code>.  <code>branch</code> means the patch has not been applied.  The <code>patch</code> state is after the patch has been applied.</p>
@@ -344,7 +337,6 @@
 <p>The second is <code>personality_enqueue_module</code>.  This function takes two parameters.  The first parameter is the name of the module to add to this test&rsquo;s queue.  The second parameter is an option list of additional flags to pass to Maven when processing it. <code>personality_enqueue_module</code> may be called as many times as necessary for your project.</p>
 <pre class="highlight plaintext"><code>NOTE: A module name of . signifies the root of the repository.
 </code></pre>
-
 <p>For example, let&rsquo;s say your project uses a special configuration to skip unit tests (-DskipTests).  Running unit tests during a javadoc build isn&rsquo;t very useful and wastes a lot of time. We can write a simple personality check to disable the unit tests:</p>
 <pre class="highlight shell"><code><span class="k">function </span>personality_modules
 <span class="o">{</span>
@@ -358,7 +350,6 @@
     ...
 
 </code></pre>
-
 <p>This function will tell test-patch that when the javadoc test is being run, do the documentation build at the base of the source repository and make sure the -DskipTests flag is passed to our build tool.</p>
 
 <h2 id="enabling-plug-ins">Enabling Plug-ins</h2>
@@ -366,7 +357,6 @@
 <p>Personalities can set the base list of plug-ins to enable and disable for their project via the <code>personality_plugins</code> function. Just call it with the same pattern as the <code>--plugins</code> command line option:</p>
 <pre class="highlight shell"><code>personality_plugins <span class="s2">"all,-checkstyle,-findbugs,-asflicense"</span>
 </code></pre>
-
 <p>This list is used if the user does not provide a list of plug-ins.</p>
 
 <h1 id="important-variables">Important Variables</h1>
@@ -377,7 +367,7 @@
 <li><p>BUILD_NATIVE will be set to true if the system has requested that non-JVM-based code be built (e.g., JNI or other compiled C code). Under Jenkins, this is always true.</p></li>
 <li><p>BUILDTOOL specifies which tool is currently being used to drive compilation.  Additionally, many build tools define xyz_ARGS to pass on to the build tool command line. (e.g., MAVEN_ARGS if maven is in use).  Projects may set this in their personality.  NOTE: today, only one build tool at a time is supported.  This may change in the future.</p></li>
 <li><p>CHANGED_FILES[@] is an array of all files that appear to be added, deleted, or modified in the patch.</p></li>
-<li><p>CHANGED_MODULES[@] is an array of all modules that house all of the CHANGED_FILES[@].  Be aware that the root of the source tree is reported as &rsquo;.&rsquo;.</p></li>
+<li><p>CHANGED_MODULES[@] is an array of all modules that house all of the CHANGED_FILES[@].  Be aware that the root of the source tree is reported as &lsquo;.&rsquo;.</p></li>
 <li><p>DOCKER_EXTRAARGS[@] is an array of command line arguments to apply to the <code>docker run</code> command.</p></li>
 <li><p>GITHUB_REPO is to help test-patch when talking to Github.  If test-patch is given just a number on the command line, it will default to using this repo to determine the pull request.</p></li>
 <li><p>JIRA_ISSUE_RE is to help test-patch when talking to JIRA.  It helps determine if the given project is appropriate for the given JIRA issue.</p></li>

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/precommit-apidocs/core/index.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/precommit-apidocs/core/index.html b/documentation/in-progress/precommit-apidocs/core/index.html
index 0db47bb..7923c0f 100644
--- a/documentation/in-progress/precommit-apidocs/core/index.html
+++ b/documentation/in-progress/precommit-apidocs/core/index.html
@@ -183,7 +183,6 @@
 </ul>
 <pre class="highlight plaintext"><code>add_bugsystem bugsystem
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -219,7 +218,6 @@
 </ul>
 <pre class="highlight plaintext"><code>add_build_tool build tool
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -255,7 +253,6 @@
 </ul>
 <pre class="highlight plaintext"><code>add_test test
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -291,7 +288,6 @@
 </ul>
 <pre class="highlight plaintext"><code>add_test_format test format
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -327,7 +323,6 @@
 </ul>
 <pre class="highlight plaintext"><code>add_test_type plugin
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -363,7 +358,6 @@
 </ul>
 <pre class="highlight plaintext"><code>delete_bugsystem bugsystem
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -399,7 +393,6 @@
 </ul>
 <pre class="highlight plaintext"><code>delete_build_tool build tool
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -435,7 +428,6 @@
 </ul>
 <pre class="highlight plaintext"><code>delete_test test
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -471,7 +463,6 @@
 </ul>
 <pre class="highlight plaintext"><code>delete_test_format test format
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -507,7 +498,6 @@
 </ul>
 <pre class="highlight plaintext"><code>delete_test_type plugin
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -543,7 +533,6 @@
 </ul>
 <pre class="highlight plaintext"><code>personality_plugins plug-in list string
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -579,7 +568,6 @@
 </ul>
 <pre class="highlight plaintext"><code>verify_needed_test test
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -617,7 +605,6 @@
 </ul>
 <pre class="highlight plaintext"><code>verify_plugin_enabled test
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -653,7 +640,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_add_array_element arrayname element
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -689,7 +675,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_array_contains element array
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -727,7 +712,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_sort_array arrayvar
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -765,7 +749,6 @@
 </ul>
 <pre class="highlight plaintext"><code>common_defaults
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -801,7 +784,6 @@
 </ul>
 <pre class="highlight plaintext"><code>patchfile_verify_zero log filename
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -837,7 +819,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_abs fsobj
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -877,7 +858,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_add_entry
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -913,7 +893,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_debug string
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -949,7 +928,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_delete_entry
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -985,7 +963,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_error string
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1021,7 +998,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_run_and_redirect filename command [..]
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1057,7 +1033,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_verify_entry
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1095,7 +1070,6 @@
 </ul>
 <pre class="highlight plaintext"><code>list_plugins
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1131,7 +1105,6 @@
 </ul>
 <pre class="highlight plaintext"><code>plugin_usage_output array
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1167,7 +1140,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_add_header header
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1203,7 +1175,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_add_option subcommand subcommanddesc
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1239,7 +1210,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_comma_to_array arrayname string
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1275,7 +1245,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_generic_columnprinter array
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1313,7 +1282,6 @@
 </ul>
 <pre class="highlight plaintext"><code>docker_version
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/precommit-apidocs/plugins/index.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/precommit-apidocs/plugins/index.html b/documentation/in-progress/precommit-apidocs/plugins/index.html
index 22d9a26..242296b 100644
--- a/documentation/in-progress/precommit-apidocs/plugins/index.html
+++ b/documentation/in-progress/precommit-apidocs/plugins/index.html
@@ -260,7 +260,6 @@
 </ul>
 <pre class="highlight plaintext"><code>maven_add_install test
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -296,7 +295,6 @@
 </ul>
 <pre class="highlight plaintext"><code>maven_delete_install test
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -334,7 +332,6 @@
 </ul>
 <pre class="highlight plaintext"><code>bugzilla_write_comment filename
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -370,7 +367,6 @@
 </ul>
 <pre class="highlight plaintext"><code>github_write_comment filename
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -406,7 +402,6 @@
 </ul>
 <pre class="highlight plaintext"><code>javac_precheck
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -444,7 +439,6 @@
 </ul>
 <pre class="highlight plaintext"><code>jira_write_comment filename
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -482,7 +476,6 @@
 </ul>
 <pre class="highlight plaintext"><code>asflicense_parse_args
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -518,7 +511,6 @@
 </ul>
 <pre class="highlight plaintext"><code>asflicense_usage
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -554,7 +546,6 @@
 </ul>
 <pre class="highlight plaintext"><code>asflicense_writexsl
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -590,7 +581,6 @@
 </ul>
 <pre class="highlight plaintext"><code>bugzilla_determine_issue
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -626,7 +616,6 @@
 </ul>
 <pre class="highlight plaintext"><code>bugzilla_http_fetch
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -662,7 +651,6 @@
 </ul>
 <pre class="highlight plaintext"><code>bugzilla_locate_patch
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -698,7 +686,6 @@
 </ul>
 <pre class="highlight plaintext"><code>bugzilla_parse_args
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -734,7 +721,6 @@
 </ul>
 <pre class="highlight plaintext"><code>bugzilla_usage
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -770,7 +756,6 @@
 </ul>
 <pre class="highlight plaintext"><code>cc_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -806,7 +791,6 @@
 </ul>
 <pre class="highlight plaintext"><code>checkstyle_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -842,7 +826,6 @@
 </ul>
 <pre class="highlight plaintext"><code>checkstyle_postapply
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -878,7 +861,6 @@
 </ul>
 <pre class="highlight plaintext"><code>checkstyle_postcompile
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -914,7 +896,6 @@
 </ul>
 <pre class="highlight plaintext"><code>checkstyle_preapply
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -950,7 +931,6 @@
 </ul>
 <pre class="highlight plaintext"><code>findbugs_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -986,7 +966,6 @@
 </ul>
 <pre class="highlight plaintext"><code>findbugs_parse_args
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1022,7 +1001,6 @@
 </ul>
 <pre class="highlight plaintext"><code>findbugs_precheck
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1058,7 +1036,6 @@
 </ul>
 <pre class="highlight plaintext"><code>findbugs_rebuild
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1094,7 +1071,6 @@
 </ul>
 <pre class="highlight plaintext"><code>findbugs_usage
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1130,7 +1106,6 @@
 </ul>
 <pre class="highlight plaintext"><code>github_breakup_url url
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1166,7 +1141,6 @@
 </ul>
 <pre class="highlight plaintext"><code>github_determine_issue
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1202,7 +1176,6 @@
 </ul>
 <pre class="highlight plaintext"><code>github_find_jira_title
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1238,7 +1211,6 @@
 </ul>
 <pre class="highlight plaintext"><code>github_jira_bridge
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1274,7 +1246,6 @@
 </ul>
 <pre class="highlight plaintext"><code>github_linecomments
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1310,7 +1281,6 @@
 </ul>
 <pre class="highlight plaintext"><code>github_locate_patch
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1346,7 +1316,6 @@
 </ul>
 <pre class="highlight plaintext"><code>github_parse_args
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1382,7 +1351,6 @@
 </ul>
 <pre class="highlight plaintext"><code>github_usage
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1418,7 +1386,6 @@
 </ul>
 <pre class="highlight plaintext"><code>initialize_java
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1454,7 +1421,6 @@
 </ul>
 <pre class="highlight plaintext"><code>javac_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1490,7 +1456,6 @@
 </ul>
 <pre class="highlight plaintext"><code>javac_initialize
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1526,7 +1491,6 @@
 </ul>
 <pre class="highlight plaintext"><code>javadoc_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1562,7 +1526,6 @@
 </ul>
 <pre class="highlight plaintext"><code>javadoc_initialize
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1598,7 +1561,6 @@
 </ul>
 <pre class="highlight plaintext"><code>jira_determine_issue
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1634,7 +1596,6 @@
 </ul>
 <pre class="highlight plaintext"><code>jira_http_fetch
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1670,7 +1631,6 @@
 </ul>
 <pre class="highlight plaintext"><code>jira_locate_patch
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1706,7 +1666,6 @@
 </ul>
 <pre class="highlight plaintext"><code>jira_parse_args
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1742,7 +1701,6 @@
 </ul>
 <pre class="highlight plaintext"><code>jira_usage
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1778,7 +1736,6 @@
 </ul>
 <pre class="highlight plaintext"><code>junit_finalize_results
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1814,7 +1771,6 @@
 </ul>
 <pre class="highlight plaintext"><code>junit_process_tests
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1850,7 +1806,6 @@
 </ul>
 <pre class="highlight plaintext"><code>maven_buildfile
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1886,7 +1841,6 @@
 </ul>
 <pre class="highlight plaintext"><code>maven_builtin_personality_file_tests
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1922,7 +1876,6 @@
 </ul>
 <pre class="highlight plaintext"><code>maven_builtin_personality_modules
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1958,7 +1911,6 @@
 </ul>
 <pre class="highlight plaintext"><code>maven_docker_support
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1994,7 +1946,6 @@
 </ul>
 <pre class="highlight plaintext"><code>maven_executor
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2030,7 +1981,6 @@
 </ul>
 <pre class="highlight plaintext"><code>maven_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2066,7 +2016,6 @@
 </ul>
 <pre class="highlight plaintext"><code>maven_initialize
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2102,7 +2051,6 @@
 </ul>
 <pre class="highlight plaintext"><code>maven_javac_logfilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2138,7 +2086,6 @@
 </ul>
 <pre class="highlight plaintext"><code>maven_modules_worker
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2174,7 +2121,6 @@
 </ul>
 <pre class="highlight plaintext"><code>maven_parse_args
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2210,7 +2156,6 @@
 </ul>
 <pre class="highlight plaintext"><code>maven_precheck
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2246,7 +2191,6 @@
 </ul>
 <pre class="highlight plaintext"><code>maven_usage
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2282,7 +2226,6 @@
 </ul>
 <pre class="highlight plaintext"><code>mvnsite_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2318,7 +2261,6 @@
 </ul>
 <pre class="highlight plaintext"><code>nobuild_buildfile
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2354,7 +2296,6 @@
 </ul>
 <pre class="highlight plaintext"><code>nobuild_builtin_personality_file_tests
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2390,7 +2331,6 @@
 </ul>
 <pre class="highlight plaintext"><code>nobuild_builtin_personality_modules
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2426,7 +2366,6 @@
 </ul>
 <pre class="highlight plaintext"><code>nobuild_executor
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2462,7 +2401,6 @@
 </ul>
 <pre class="highlight plaintext"><code>nobuild_modules_worker
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2498,7 +2436,6 @@
 </ul>
 <pre class="highlight plaintext"><code>perlcritic_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2534,7 +2471,6 @@
 </ul>
 <pre class="highlight plaintext"><code>perlcritic_parse_args
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2570,7 +2506,6 @@
 </ul>
 <pre class="highlight plaintext"><code>perlcritic_postapply
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2606,7 +2541,6 @@
 </ul>
 <pre class="highlight plaintext"><code>perlcritic_postcompile
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2642,7 +2576,6 @@
 </ul>
 <pre class="highlight plaintext"><code>perlcritic_preapply
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2678,7 +2611,6 @@
 </ul>
 <pre class="highlight plaintext"><code>perlcritic_precheck
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2714,7 +2646,6 @@
 </ul>
 <pre class="highlight plaintext"><code>perlcritic_usage
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2750,7 +2681,6 @@
 </ul>
 <pre class="highlight plaintext"><code>pylint_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2786,7 +2716,6 @@
 </ul>
 <pre class="highlight plaintext"><code>pylint_parse_args
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2822,7 +2751,6 @@
 </ul>
 <pre class="highlight plaintext"><code>pylint_postapply
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2858,7 +2786,6 @@
 </ul>
 <pre class="highlight plaintext"><code>pylint_postcompile
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2894,7 +2821,6 @@
 </ul>
 <pre class="highlight plaintext"><code>pylint_preapply
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2930,7 +2856,6 @@
 </ul>
 <pre class="highlight plaintext"><code>pylint_precheck
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -2966,7 +2891,6 @@
 </ul>
 <pre class="highlight plaintext"><code>pylint_usage
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3002,7 +2926,6 @@
 </ul>
 <pre class="highlight plaintext"><code>rubocop_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3038,7 +2961,6 @@
 </ul>
 <pre class="highlight plaintext"><code>rubocop_parse_args
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3074,7 +2996,6 @@
 </ul>
 <pre class="highlight plaintext"><code>rubocop_postapply
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3110,7 +3031,6 @@
 </ul>
 <pre class="highlight plaintext"><code>rubocop_postcompile
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3146,7 +3066,6 @@
 </ul>
 <pre class="highlight plaintext"><code>rubocop_preapply
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3182,7 +3101,6 @@
 </ul>
 <pre class="highlight plaintext"><code>rubocop_precheck
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3218,7 +3136,6 @@
 </ul>
 <pre class="highlight plaintext"><code>rubocop_usage
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3254,7 +3171,6 @@
 </ul>
 <pre class="highlight plaintext"><code>ruby_lint_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3290,7 +3206,6 @@
 </ul>
 <pre class="highlight plaintext"><code>ruby_lint_parse_args
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3326,7 +3241,6 @@
 </ul>
 <pre class="highlight plaintext"><code>ruby_lint_postapply
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3362,7 +3276,6 @@
 </ul>
 <pre class="highlight plaintext"><code>ruby_lint_postcompile
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3398,7 +3311,6 @@
 </ul>
 <pre class="highlight plaintext"><code>ruby_lint_preapply
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3434,7 +3346,6 @@
 </ul>
 <pre class="highlight plaintext"><code>ruby_lint_precheck
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3470,7 +3381,6 @@
 </ul>
 <pre class="highlight plaintext"><code>ruby_lint_usage
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3506,7 +3416,6 @@
 </ul>
 <pre class="highlight plaintext"><code>scalac_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3542,7 +3451,6 @@
 </ul>
 <pre class="highlight plaintext"><code>scaladoc_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3578,7 +3486,6 @@
 </ul>
 <pre class="highlight plaintext"><code>shelldocs_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3614,7 +3521,6 @@
 </ul>
 <pre class="highlight plaintext"><code>shelldocs_parse_args
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3650,7 +3556,6 @@
 </ul>
 <pre class="highlight plaintext"><code>shelldocs_postapply
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3686,7 +3591,6 @@
 </ul>
 <pre class="highlight plaintext"><code>shelldocs_postcompile
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3722,7 +3626,6 @@
 </ul>
 <pre class="highlight plaintext"><code>shelldocs_preapply
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3758,7 +3661,6 @@
 </ul>
 <pre class="highlight plaintext"><code>shelldocs_precheck
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3794,7 +3696,6 @@
 </ul>
 <pre class="highlight plaintext"><code>shelldocs_private_findbash
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3830,7 +3731,6 @@
 </ul>
 <pre class="highlight plaintext"><code>shelldocs_usage
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3866,7 +3766,6 @@
 </ul>
 <pre class="highlight plaintext"><code>tap_finalize_results
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3902,7 +3801,6 @@
 </ul>
 <pre class="highlight plaintext"><code>tap_parse_args
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3938,7 +3836,6 @@
 </ul>
 <pre class="highlight plaintext"><code>tap_process_tests
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -3974,7 +3871,6 @@
 </ul>
 <pre class="highlight plaintext"><code>tap_usage
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -4010,7 +3906,6 @@
 </ul>
 <pre class="highlight plaintext"><code>unitveto_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -4046,7 +3941,6 @@
 </ul>
 <pre class="highlight plaintext"><code>unitveto_parse_args
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -4082,7 +3976,6 @@
 </ul>
 <pre class="highlight plaintext"><code>unitveto_patchfile
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -4118,7 +4011,6 @@
 </ul>
 <pre class="highlight plaintext"><code>unitveto_usage
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -4154,7 +4046,6 @@
 </ul>
 <pre class="highlight plaintext"><code>whitespace_linecomment_reporter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -4190,7 +4081,6 @@
 </ul>
 <pre class="highlight plaintext"><code>whitespace_postcompile
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -4226,7 +4116,6 @@
 </ul>
 <pre class="highlight plaintext"><code>xml_filefilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -4262,7 +4151,6 @@
 </ul>
 <pre class="highlight plaintext"><code>xml_postcompile
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -4298,7 +4186,6 @@
 </ul>
 <pre class="highlight plaintext"><code>xml_precheck
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/precommit-apidocs/smart-apply-patch/index.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/precommit-apidocs/smart-apply-patch/index.html b/documentation/in-progress/precommit-apidocs/smart-apply-patch/index.html
index 6ac9d5d..09b916b 100644
--- a/documentation/in-progress/precommit-apidocs/smart-apply-patch/index.html
+++ b/documentation/in-progress/precommit-apidocs/smart-apply-patch/index.html
@@ -149,7 +149,6 @@
 </ul>
 <pre class="highlight plaintext"><code>setup_defaults
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -185,7 +184,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_usage
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -223,7 +221,6 @@
 </ul>
 <pre class="highlight plaintext"><code>add_footer_table
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -259,7 +256,6 @@
 </ul>
 <pre class="highlight plaintext"><code>add_test
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -295,7 +291,6 @@
 </ul>
 <pre class="highlight plaintext"><code>add_vote_table
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -331,7 +326,6 @@
 </ul>
 <pre class="highlight plaintext"><code>big_console_header
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/precommit-apidocs/test-patch/index.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/precommit-apidocs/test-patch/index.html b/documentation/in-progress/precommit-apidocs/test-patch/index.html
index fa5b982..4822592 100644
--- a/documentation/in-progress/precommit-apidocs/test-patch/index.html
+++ b/documentation/in-progress/precommit-apidocs/test-patch/index.html
@@ -202,7 +202,6 @@
 </ul>
 <pre class="highlight plaintext"><code>relative_dir path
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -240,7 +239,6 @@
 </ul>
 <pre class="highlight plaintext"><code>verify_multijdk_test test
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -280,7 +278,6 @@
 </ul>
 <pre class="highlight plaintext"><code>add_footer_table subsystem string
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -316,7 +313,6 @@
 </ul>
 <pre class="highlight plaintext"><code>add_header_line string
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -352,7 +348,6 @@
 </ul>
 <pre class="highlight plaintext"><code>add_test_table failurereason testlist
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -388,7 +383,6 @@
 </ul>
 <pre class="highlight plaintext"><code>add_vote_table +1/0/-1 subsystem string
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -424,7 +418,6 @@
 </ul>
 <pre class="highlight plaintext"><code>big_console_header string
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -460,7 +453,6 @@
 </ul>
 <pre class="highlight plaintext"><code>clock_display seconds
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -496,7 +488,6 @@
 </ul>
 <pre class="highlight plaintext"><code>echo_and_redirect filename command [..]
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -532,7 +523,6 @@
 </ul>
 <pre class="highlight plaintext"><code>generate_stack
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -568,7 +558,6 @@
 </ul>
 <pre class="highlight plaintext"><code>module_file_fragment module
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -604,7 +593,6 @@
 </ul>
 <pre class="highlight plaintext"><code>offset_clock seconds
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -640,7 +628,6 @@
 </ul>
 <pre class="highlight plaintext"><code>setup_defaults
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -676,7 +663,6 @@
 </ul>
 <pre class="highlight plaintext"><code>start_clock
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -712,7 +698,6 @@
 </ul>
 <pre class="highlight plaintext"><code>stop_clock
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -748,7 +733,6 @@
 </ul>
 <pre class="highlight plaintext"><code>write_comment filename
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -784,7 +768,6 @@
 </ul>
 <pre class="highlight plaintext"><code>yetus_usage
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -822,7 +805,6 @@
 </ul>
 <pre class="highlight plaintext"><code>archive
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -858,7 +840,6 @@
 </ul>
 <pre class="highlight plaintext"><code>bugsystem_linecomments filename
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -894,7 +875,6 @@
 </ul>
 <pre class="highlight plaintext"><code>buildtool_cwd MODULE_ index
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -930,7 +910,6 @@
 </ul>
 <pre class="highlight plaintext"><code>calcdiffs branchlog patchlog testtype
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -966,7 +945,6 @@
 </ul>
 <pre class="highlight plaintext"><code>clear_personality_queue
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1002,7 +980,6 @@
 </ul>
 <pre class="highlight plaintext"><code>column_calcdiffs branchlog patchlog
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1038,7 +1015,6 @@
 </ul>
 <pre class="highlight plaintext"><code>compile branch|patch
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1076,7 +1052,6 @@
 </ul>
 <pre class="highlight plaintext"><code>compile_cycle branch|patch
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1114,7 +1089,6 @@
 </ul>
 <pre class="highlight plaintext"><code>compile_jvm branch|patch
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1152,7 +1126,6 @@
 </ul>
 <pre class="highlight plaintext"><code>compile_nonjvm branch|patch
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1190,7 +1163,6 @@
 </ul>
 <pre class="highlight plaintext"><code>dequeue_personality_module modulenames
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1226,7 +1198,6 @@
 </ul>
 <pre class="highlight plaintext"><code>distclean
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1264,7 +1235,6 @@
 </ul>
 <pre class="highlight plaintext"><code>error_calcdiffs branchlog patchlog
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1300,7 +1270,6 @@
 </ul>
 <pre class="highlight plaintext"><code>generic_calcdiff_status totalbranchissues totalpatchissues newpatchissues
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1336,7 +1305,6 @@
 </ul>
 <pre class="highlight plaintext"><code>generic_logfilter
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1372,7 +1340,6 @@
 </ul>
 <pre class="highlight plaintext"><code>generic_post_handler origlog testtype multijdkmode run commands
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1410,7 +1377,6 @@
 </ul>
 <pre class="highlight plaintext"><code>generic_postlog_compare origlog testtype multijdkmode
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1448,7 +1414,6 @@
 </ul>
 <pre class="highlight plaintext"><code>generic_pre_handler testype multijdk
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1486,7 +1451,6 @@
 </ul>
 <pre class="highlight plaintext"><code>initialize $@
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1524,7 +1488,6 @@
 </ul>
 <pre class="highlight plaintext"><code>module_status moduleindex -1-0|0|+1 logvalue message
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1560,7 +1523,6 @@
 </ul>
 <pre class="highlight plaintext"><code>modules_backup
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1596,7 +1558,6 @@
 </ul>
 <pre class="highlight plaintext"><code>modules_messages repostatus testtype summarymode
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1632,7 +1593,6 @@
 </ul>
 <pre class="highlight plaintext"><code>modules_reset
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1668,7 +1628,6 @@
 </ul>
 <pre class="highlight plaintext"><code>modules_restore
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1704,7 +1663,6 @@
 </ul>
 <pre class="highlight plaintext"><code>modules_workers repostatus testtype mvncmdline
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1740,7 +1698,6 @@
 </ul>
 <pre class="highlight plaintext"><code>patchfiletests branch|patch
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1778,7 +1735,6 @@
 </ul>
 <pre class="highlight plaintext"><code>personality_enqueue_module module profiles/flags/etc
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1816,7 +1772,6 @@
 </ul>
 <pre class="highlight plaintext"><code>prepopulate_footer
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1852,7 +1807,6 @@
 </ul>
 <pre class="highlight plaintext"><code>report_jvm_version directory
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>
@@ -1890,7 +1844,6 @@
 </ul>
 <pre class="highlight plaintext"><code>verify_patchdir_still_exists
 </code></pre>
-
 <ul>
 <li>Description</li>
 </ul>

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/precommit-architecture/index.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/precommit-architecture/index.html b/documentation/in-progress/precommit-architecture/index.html
index e6ebcf6..c5db746 100644
--- a/documentation/in-progress/precommit-architecture/index.html
+++ b/documentation/in-progress/precommit-architecture/index.html
@@ -191,7 +191,7 @@
 
 <h2 id="compile-cycle-patch">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 &#39;after&rsquo; 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 &lsquo;after&rsquo; checks are performed.</p>
 
 <h2 id="unit-tests">Unit Tests</h2>
 

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/precommit-basic/index.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/precommit-basic/index.html b/documentation/in-progress/precommit-basic/index.html
index d578a3b..9d08b50 100644
--- a/documentation/in-progress/precommit-basic/index.html
+++ b/documentation/in-progress/precommit-basic/index.html
@@ -224,19 +224,15 @@ as a whole.</p>
 <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
 </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> &lt;other options&gt;
 </code></pre>
-
 <p>As a short-cut, every plug-in may be enabled via the special &lsquo;all&rsquo; 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> &lt;other options&gt;
 </code></pre>
-
 <p><code>--plugins</code> also allows some basic <q>arithmetic</q>:</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> &lt;other options&gt;
 </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>
@@ -245,14 +241,12 @@ as a whole.</p>
 <pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">cd</span> &lt;your repo&gt;
 <span class="gp">$ </span><span class="nb">test</span>-patch.sh --dirty-workspace --project<span class="o">=</span>projectname &lt;filename&gt;
 </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 &ndash;run-tests option:</p>
 <pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">cd</span> &lt;your repo&gt;
 <span class="gp">$ </span><span class="nb">test</span>-patch.sh --dirty-workspace --run-tests &lt;filename&gt;
 </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>
@@ -261,7 +255,6 @@ as a whole.</p>
 <span class="gp">$ </span><span class="nb">cd</span> ../&lt;testrepo&gt;
 <span class="gp">$ </span><span class="nb">test</span>-patch.sh --basedir<span class="o">=</span>&lt;testrepo&gt; --resetrepo /tmp/patchfile
 </code></pre>
-
 <p>We used two new options here.  &ndash;basedir sets the location of the repository to use for testing.  &ndash;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>
 
 <h1 id="automation">Automation</h1>
@@ -271,22 +264,18 @@ as a whole.</p>
 <p>For example:</p>
 <pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh --robot --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
 </code></pre>
-
 <p>&hellip; will trigger test-patch to run in fully automated 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.  This will always run the unit tests, write answers back to bug systems, remove old, stopped/exited Docker containers after 24 hours and images after 1 week, forcibly use &ndash;resetrepo, and more.  The &ndash;build-url option is also useful when running in &ndash;robot mode so that emails and such
 have a location to look at the output artifacts:</p>
 <pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh --robot --build-url<span class="o">=</span>http://server.example.name:80/<span class="k">${</span><span class="nv">buildnumber</span><span class="k">}</span>/
 </code></pre>
-
 <p>Some plug-ins such as Maven have special handling if there are multiple executions of test-patch happening at once.  It is very common when using automation systems to have multiple runs on the same host. In order to assist these plug-ins, an instance identifier may be provided:</p>
 <pre class="highlight shell"><code><span class="gp">$ </span><span class="nb">test</span>-patch.sh --robot --instance<span class="o">=</span>1
 </code></pre>
-
 <p>If &ndash;robot is specified without an instance, a random number is generated and used.</p>
 
 <p>There is some special handling if Jenkins is actually your automation tool.  Instead of using &ndash;robot, use &ndash;jenkins:</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
 </code></pre>
-
 <p>This will enable &ndash;robot, set the &ndash;build-url option from the ${BUILD_URL} environment variable, and the instance identifier is set to the ${EXECUTOR_NUMBER}.</p>
 
 <p>If stuck containers are a problem, a more aggressive robot may be enabled with the &ndash;sentinel option.  This option enables killing containers that have been running for over 24 hours as well.</p>
@@ -296,7 +285,6 @@ have a location to look at the output artifacts:</p>
 <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
 </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>
@@ -311,13 +299,11 @@ have a location to look at the output artifacts:</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
 </code></pre>
-
 <p>&hellip; 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
 </code></pre>
-
 <p>&hellip; 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>
@@ -325,15 +311,12 @@ have a location to look at the output artifacts:</p>
 <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
 </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
 </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
 </code></pre>
-
 <p>&hellip; will process PR #99 on the apache/pig repo.</p>
 
 <h2 id="generic-urls">Generic URLs</h2>
@@ -343,7 +326,6 @@ have a location to look at the output artifacts:</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
 </code></pre>
-
 <p>&hellip; will download and process the file.patch from the example.com webserver.</p>
 
 <h1 id="project-specific-capabilities">Project-specific Capabilities</h1>
@@ -353,7 +335,6 @@ have a location to look at the output artifacts:</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>
 </code></pre>
-
 <p>This tells test-patch to use the personality in the given file.</p>
 
 <h2 id="project-method">Project Method</h2>
@@ -361,13 +342,11 @@ have a location to look at the output artifacts:</p>
 <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>
 <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>
 </code></pre>
-
 <h1 id="multijdk">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 &ndash;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>
 </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&ndash;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>
@@ -377,7 +356,6 @@ have a location to look at the output artifacts:</p>
 <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
 </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>

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/precommit-bugsystems/index.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/precommit-bugsystems/index.html b/documentation/in-progress/precommit-bugsystems/index.html
index 83a1568..821258f 100644
--- a/documentation/in-progress/precommit-bugsystems/index.html
+++ b/documentation/in-progress/precommit-bugsystems/index.html
@@ -127,7 +127,6 @@
 <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 &lt;pluginname&gt;
 </code></pre>
-
 <ul>
 <li><p>pluginname_locate_patch</p>
 
@@ -166,7 +165,6 @@
 <p>Currently, Bugzilla support is read-only.  To use it, the Bug ID must be preferenced with &lsquo;BZ:&rsquo;.  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
 </code></pre>
-
 <p>&hellip; 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&rsquo;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>

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/precommit-buildtools/index.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/precommit-buildtools/index.html b/documentation/in-progress/precommit-buildtools/index.html
index 7f4822e..7f87717 100644
--- a/documentation/in-progress/precommit-buildtools/index.html
+++ b/documentation/in-progress/precommit-buildtools/index.html
@@ -127,7 +127,6 @@
 <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 &lt;pluginname&gt;
 </code></pre>
-
 <h1 id="global-variables">Global Variables</h1>
 
 <ul>
@@ -151,7 +150,6 @@
 <p>This allows for custom directories to be created and used as necessary.</p>
 <pre class="highlight plaintext"><code>The default is module.
 </code></pre>
-
 <ul>
 <li><p>UNSUPPORTED_TEST</p>
 
@@ -178,12 +176,12 @@
 <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 &lsquo;test&rsquo; to trigger &#39;unit&rsquo; tests, then <code>module_workers</code> should be called with &#39;test&rsquo; 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 &lsquo;test&rsquo; to trigger &lsquo;unit&rsquo; tests, then <code>module_workers</code> should be called with &lsquo;test&rsquo; appended onto its normal parameters.</li>
 </ul></li>
 <li><p>pluginname_builtin_personality_modules</p>
 
 <ul>
-<li>Default method to determine how to enqueue modules for processing.  Note that personalities may override this function. Requires two arguments: repo status and test desired. For example, in a maven build, values may be &#39;branch&rsquo; and &#39;mvninstall&rsquo;.</li>
+<li>Default method to determine how to enqueue modules for processing.  Note that personalities may override this function. Requires two arguments: repo status and test desired. For example, in a maven build, values may be &lsquo;branch&rsquo; and &lsquo;mvninstall&rsquo;.</li>
 </ul></li>
 <li><p>pluginname_builtin_personality_file_tests</p>
 
@@ -249,7 +247,7 @@
 
 <h1 id="cmake-specific">CMAKE Specific</h1>
 
-<p>By default, cmake will create a &#39;build&rsquo; directory and perform all work there.  This may be changed either on the command line or via a personality setting.  cmake requires make to be enabled.</p>
+<p>By default, cmake will create a &lsquo;build&rsquo; directory and perform all work there.  This may be changed either on the command line or via a personality setting.  cmake requires make to be enabled.</p>
 
 <h1 id="gradle-specific">Gradle Specific</h1>
 

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/precommit-qbt/index.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/precommit-qbt/index.html b/documentation/in-progress/precommit-qbt/index.html
index 35871b4..6f2e013 100644
--- a/documentation/in-progress/precommit-qbt/index.html
+++ b/documentation/in-progress/precommit-qbt/index.html
@@ -139,7 +139,6 @@ file. This can then be used with systems like Jenkin&rsquo;s
 email-ext plug-in to send the output as an emailed report:</p>
 <pre class="highlight plaintext"><code>${FILE,path="&lt;report-file-path&gt;"}
 </code></pre>
-
 <p>For something a bit more structured, there is also the <code>--html-report-file</code>
 option.  Using this output, again with Jenkins&rsquo; email-ext plug-in, it is
 possible to build some very nice looking output that is easily customized:</p>
@@ -162,7 +161,6 @@ possible to build some very nice looking output that is easily customized:</p>
 ${FILE,path="<span class="nt">&lt;report-file-path&gt;</span>"}
 <span class="nt">&lt;/body&gt;&lt;/html&gt;</span>
 </code></pre>
-
 <p>If your mailing lists do not allow HTML-formatted email, then the <code>--brief-report-file</code>
 provides a solution.  This option creates a very plain, reduced content text file
 suitable for email.  It contains just the barebones information needed to get

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/precommit-smart-apply-patch/index.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/precommit-smart-apply-patch/index.html b/documentation/in-progress/precommit-smart-apply-patch/index.html
index 7d45173..d77518a 100644
--- a/documentation/in-progress/precommit-smart-apply-patch/index.html
+++ b/documentation/in-progress/precommit-smart-apply-patch/index.html
@@ -131,17 +131,14 @@
 <p>Its simplest 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
 </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
 </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
 </code></pre>
-
 <p>that in addition to applying the patch will also attempt to:</p>
 
 <ul>

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/precommit-testformats/index.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/precommit-testformats/index.html b/documentation/in-progress/precommit-testformats/index.html
index bda3331..e1a6986 100644
--- a/documentation/in-progress/precommit-testformats/index.html
+++ b/documentation/in-progress/precommit-testformats/index.html
@@ -127,7 +127,6 @@
 <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 &lt;pluginname&gt;
 </code></pre>
-
 <p>Test format plugins can provide following two methods, which will be called by test-patch if defined.</p>
 
 <ul>

http://git-wip-us.apache.org/repos/asf/yetus/blob/012f133c/documentation/in-progress/releasedocmaker/index.html
----------------------------------------------------------------------
diff --git a/documentation/in-progress/releasedocmaker/index.html b/documentation/in-progress/releasedocmaker/index.html
index 0852f50..76f00e5 100644
--- a/documentation/in-progress/releasedocmaker/index.html
+++ b/documentation/in-progress/releasedocmaker/index.html
@@ -165,7 +165,6 @@
 <p>Minimally, the name of the JIRA project and a version registered in JIRA must be provided:</p>
 <pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker.py --project <span class="o">(</span>project<span class="o">)</span> --version <span class="o">(</span>version<span class="o">)</span>
 </code></pre>
-
 <p>This will query Apache JIRA, generating two files in a directory named after the given version in an extended markdown format which can be processed by both mvn site and GitHub.</p>
 
 <ul>
@@ -183,20 +182,17 @@
 <p>For example, to build the release documentation for HBase v1.2.0&hellip;</p>
 <pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker.py --project HBASE --version 1.2.0
 </code></pre>
-
 <p>&hellip; will create a 1.2.0 directory and inside that directory will be CHANGES.1.2.0.md and RELEASENOTES.1.2.0.md .</p>
 
 <p>By default, release notes are expected to be in plain text.  However, you can write them in markdown if you include a header at the top of your release note:</p>
 <pre class="highlight xml"><code><span class="c">&lt;!-- markdown --&gt;</span>
 remaining text
 </code></pre>
-
 <h1 id="changing-the-header">Changing the Header</h1>
 
 <p>By default, it will use a header that matches the project name.  But that is kind of ugly and the case may be wrong.  Luckily, the title can be changed:</p>
 <pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker.py --project HBASE --version 1.2.0 --projecttitle <span class="s2">"Apache HBase"</span>
 </code></pre>
-
 <p>Now instead of <q>HBASE</q>, it will use <q>Apache HBASE</q> for some titles and headers.</p>
 
 <h1 id="multiple-versions">Multiple Versions</h1>
@@ -204,13 +200,11 @@ remaining text
 <p>The script can also generate multiple versions at once, by</p>
 <pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker.py --project HBASE --version 1.0.0 --version 1.2.0
 </code></pre>
-
 <p>This will create the files for versions 1.0.0 and versions 1.2.0 in their own directories.</p>
 
 <p>But what if the version numbers are not known?  releasedocmaker can also generate version data based upon ranges:</p>
 <pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker.py --project HBASE --version 1.0.0 --version 1.2.0 --range
 </code></pre>
-
 <p>In this form, releasedocmaker will query JIRA, discover all versions that alphabetically appear to be between 1.0.0 and 1.2.0, inclusive, and generate all of the relative release documents.  This is especially useful when bootstrapping an existing project.</p>
 
 <h1 id="unreleased-dates">Unreleased Dates</h1>
@@ -220,7 +214,6 @@ remaining text
 <p>The &ndash;usetoday option can be used to signify that instead of using Unreleased, releasedocmaker should use today&rsquo;s date.</p>
 <pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker.py --project HBASE --version 1.0.0 --usetoday
 </code></pre>
-
 <p>After using this option and release, don&rsquo;t forget to change JIRA&rsquo;s release date to match!</p>
 
 <h1 id="sorted-output">Sorted Output</h1>
@@ -232,11 +225,9 @@ remaining text
 <p>By default, releasedocmaker will sort the output based upon the resolution date of the issue starting with older resolutions.  This is the same as giving these options:</p>
 <pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker.py --project falcon --version 0.6 --sorttype resolutiondate --sortorder older
 </code></pre>
-
 <p>The order can be reversed so that newer issues appear on top by providing the &lsquo;newer&rsquo; flag:</p>
 <pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker.py --project falcon --version 0.6 --sorttype resolutiondate --sortorder newer
 </code></pre>
-
 <p>In the case of multiple projects given on the command line, the projects will be interspersed.</p>
 
 <h2 id="issue-number-based-sort">Issue Number-based Sort</h2>
@@ -244,27 +235,23 @@ remaining text
 <p>An alternative to the date-based sort is to sort based upon the issue id.  This may be accomplished via:</p>
 <pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker.py --project falcon --version 0.6 --sorttype issueid --sortorder asc
 </code></pre>
-
 <p>This will now sort by the issue id, listing them in lowest to highest (or ascending) order.</p>
 
 <p>The order may be reversed to list them in highest to lowest (or descending) order by providing the appropriate flag:</p>
 <pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker.py --project falcon --version 0.6 --sorttype issueid --sortorder desc
 </code></pre>
-
 <p>In the case of multiple projects given on the command line, the projects will be grouped and then sorted by issue id.</p>
 
 <h1 id="backward-incompatible-changes">Backward Incompatible Changes</h1>
 
 <p>To check if an issue is backward-incompatible the releasedocmaker script first checks the <q>Hadoop Flags</q> field in the
-issue. If this field is found to be blank then it searches for the &#39;backward-incompatible&rsquo; label. You can override the
+issue. If this field is found to be blank then it searches for the &lsquo;backward-incompatible&rsquo; label. You can override the
 default value for this label by using &ndash;incompatiblelabel option e.g.</p>
 <pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker.py --project falcon --version 0.6 --incompatiblelabel not-compatible
 </code></pre>
-
 <p>or equivalently using the shorter -X option</p>
 <pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker.py --project falcon --version 0.6 -X not-compatible
 </code></pre>
-
 <h1 id="lint-mode">Lint Mode</h1>
 
 <p>In order to ensure proper formatting while using mvn site, releasedocmaker puts in periods (.) for fields that are empty or unassigned.  This can be unsightly and not proper for any given project.  There are also other things, such as missing release notes for incompatible changes, that are less than desirable.</p>
@@ -272,7 +259,6 @@ default value for this label by using &ndash;incompatiblelabel option e.g.</p>
 <p>In order to help release managers from having to scan through potentially large documents, releasedocmaker features a lint mode, triggered via &ndash;lint:</p>
 <pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker.py --project HBASE --version 1.0.0 --lint
 </code></pre>
-
 <p>This will do the normal JIRA querying, looking for items it considers problematic.  It will print the information to the screen and then exit with either success or failure, depending upon if any issues were discovered.</p>
 
 <h1 id="index-mode">Index Mode</h1>
@@ -290,7 +276,6 @@ For example directories with names like 0.6, 1.2.2, 1.2alpha etc. will all be li
 <p>You can find the version of the releasedocmaker that you are using by giving the -V option. This may be helpful in finding documentation for the version you are using.</p>
 <pre class="highlight shell"><code><span class="gp">$ </span>releasedocmaker.py -V
 </code></pre>
-
     </div>
       <div class="container">
     <hr>


Mime
View raw message