Author: buildbot
Date: Wed Aug 19 22:58:05 2015
New Revision: 962393

Log:
Staging update by buildbot for maven

Modified:
    websites/staging/maven/trunk/content/   (props changed)
    
websites/staging/maven/trunk/content/developers/website/deploy-component-reference-documentation.html
    websites/staging/maven/trunk/content/maven-site-1.0-site.jar

Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Aug 19 22:58:05 2015
@@ -1 +1 @@
-1696667
+1696687

Modified: 
websites/staging/maven/trunk/content/developers/website/deploy-component-reference-documentation.html
==============================================================================
--- 
websites/staging/maven/trunk/content/developers/website/deploy-component-reference-documentation.html
 (original)
+++ 
websites/staging/maven/trunk/content/developers/website/deploy-component-reference-documentation.html
 Wed Aug 19 22:58:05 2015
@@ -449,7 +449,7 @@ Hervé Boutemy" />
                                   
             <!-- Licensed to the Apache Software Foundation (ASF) under one 
--><!-- or more contributor license agreements.  See the NOTICE file --><!-- 
distributed with this work for additional information --><!-- regarding 
copyright ownership.  The ASF licenses this file --><!-- to you under the 
Apache License, Version 2.0 (the --><!-- "License"); you may not use this file 
except in compliance --><!-- with the License.  You may obtain a copy of the 
License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  
--><!-- Unless required by applicable law or agreed to in writing, --><!-- 
software distributed under the License is distributed on an --><!-- "AS IS" 
BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or 
implied.  See the License for the --><!-- specific language governing 
permissions and limitations --><!-- under the License. --><!-- NOTE: For help 
with the syntax of this file, see: --><!-- 
http://maven.apache.org/doxia/references/
 apt-format.html --><div class="section">
 <h2><a name="Introduction"></a>Introduction</h2>
-<p>This document gives step-by-step instructions for deploying Maven 
components reference documentation inside the Maven <a class="externalLink" 
href="http://maven.apache.org";>http://maven.apache.org</a> website.</p>
+<p>This document gives step-by-step instructions for deploying Maven 
components reference documentation inside the Maven <a class="externalLink" 
href="http://maven.apache.org/";>http://maven.apache.org/</a> website.</p>
 <p>See <a href="./index.html">Maven website introduction</a> for instructions 
on the whole website publication (main site content + components).</p></div>
 <div class="section">
 <h2><a name="Overview"></a>Overview</h2>
@@ -459,9 +459,9 @@ Hervé Boutemy" />
 <p>Components don't use CMS: components reference documentation are versioned 
and generated from full sources, with both handwritten content (like Maven main 
site) and content generated from sources (javadoc, unit-test results, 
integration test results...).</p>
 <div class="section">
 <h3><a name="Staging_component_reference_documentation"></a>Staging component 
reference documentation</h3>
-<p>Reference documentation of a component is staged in 
<tt>http://maven.apache.org/xxx-archives/yyy-LATEST</tt>, where <tt>yyy</tt> is 
the component name and <tt>xxx</tt> can be:</p>
+<p>Reference documentation of a component is staged in 
<tt>http://maven.apache.org/xxx-archives/yyy-LATEST/</tt>, where <tt>yyy</tt> 
is the component name and <tt>xxx</tt> can be:</p>
 <ul>
-<li>the component type, like <tt>shared</tt>, <tt>plugins</tt>, 
<tt>skins</tt>, ... (see <a href="/shared-archives/">/shared-archives/</a>, <a 
href="/plugins-archives/">/plugins-archives/</a>, <a 
href="/skins-archives/">/skins-archives/</a>)</li>
+<li>the component type, like <tt>shared</tt>, <tt>plugins</tt>, 
<tt>skins</tt>, ... (see <a href="/shared-archives/">/shared-archives/</a>, <a 
href="/plugins-archives/">/plugins-archives/</a>, <a 
href="/plugin-tools-archives/">/plugin-tools-archives/</a>, <a 
href="/pom-archives/">/pom-archives/</a>, <a 
href="/scm-archives/">/scm-archives/</a>, <a 
href="/skins-archives/">/skins-archives/</a>, <a 
href="/surefire-archives/">/surefire-archives/</a>, ...)</li>
 <li>the component name for standalone components, like <tt>archetype</tt>, 
<tt>plugin-tools</tt>, <tt>surefire</tt>, <tt>wagon</tt>, ... (see <a 
href="/archetype-archives/">/archetype-archives/</a>, <a 
href="/plugin-tools-archives/">/plugin-tools-archives/</a>, <a 
href="/surefire-archives/">/surefire-archives/</a>, <a 
href="/wagon-archives/">/wagon-archives/</a>)</li></ul>
 <p>To publish component reference documentation:</p>
 <ol style="list-style-type: decimal">
@@ -474,7 +474,7 @@ Hervé Boutemy" />
 <li>stage the reference documentation to website production svn area, using <a 
href="/plugins/maven-scm-publish-plugin">maven-scm-publish-plugin</a>: (TODO: 
explanations on configuration in pom to yyy-LATEST)
 <div class="source"><pre class="prettyprint linenums">mvn 
scm-publish:publish-scm</pre></div>
 <p>svnpubsub mechanism transfers svn production content to live production 
site</p></li></ol>
-<p><b>Notice</b>: content is in fact published to <a 
href="/components/">/components/</a> directory, and rewrite rules in 
<tt>.htaccess</tt> detect files not found in main site to try <a 
href="/components/">/components/</a> content instead.</p></div>
+<p><b>Notice</b>: content is in fact published to <a 
href="/components/">/components/</a> directory, and rewrite rules in 
<tt>.htaccess</tt> detect files not found in main site to try <a 
href="/components/">/components/</a> content instead (see <a 
class="externalLink" 
href="https://issues.apache.org/jira/browse/MPOM-80";>MPOM-80</a>.</p></div>
 <div class="section">
 <h3><a 
name="Publishing_versioned_component_reference_documentation"></a>Publishing 
versioned component reference documentation</h3>
 <p>When doing a release, yyy-LATEST content staged in previous section 
needs:</p>

Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.


Reply via email to