svn commit: r1830652 - in /maven/website/content: developers/website/deploy-component-reference-documentation.html maven-site-1.0-site.jar

[sv...@apache.org]

Author: svn-site-role
Date: Tue May  1 04:01:17 2018
New Revision: 1830652

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/developers/website/deploy-component-reference-documentation.html
    maven/website/content/maven-site-1.0-site.jar

Modified: maven/website/content/developers/website/deploy-component-reference-documentation.html
==============================================================================
--- maven/website/content/developers/website/deploy-component-reference-documentation.html (original)
+++ maven/website/content/developers/website/deploy-component-reference-documentation.html Tue May  1 04:01:17 2018
@@ -135,7 +135,7 @@ Hervé Boutemy" />
         <div id="bodyColumn"  class="span10" >
 <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 href="/">http:s//maven.apache.org/</a> website.</p>
+<p>This document gives step-by-step instructions for deploying Maven components reference documentation inside the Maven <a href="/">https://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>
@@ -145,7 +145,7 @@ 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>https://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="/pom-archives/">/pom-archives/</a>, <a href="/skins-archives/">/skins-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="/archetypes-archives/">/archetypes-archives/</a>, <a href="/plugin-tools-archives/">/plugin-tools-archives/</a>, <a href="/scm-archives/">/scm-archives/</a>, <a href="/surefire-archives/">/surefire-archives/</a>, <a href="/wagon-archives/">/wagon-archives/</a>)</li></ul>
@@ -160,7 +160,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 (see <a class="externalLink" href="https://issues.apache.org/jira/browse/MPOM-80">MPOM-80</a>).</p></div>
+<p><b>Notice</b>: content is in fact published to <a href="/components/">/components/</a> directory, and symbolic links declared in <tt>resources/**/components.links</tt> in main site source are used by Ant to create a reference from <tt>/xxx</tt> (= what we want to be user-visible) to <tt>/components/xxx</tt> (what what is checked out).</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, <tt>yyy-LATEST</tt> content staged in previous section needs:</p>

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