You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by bu...@apache.org on 2014/03/12 22:30:53 UTC
svn commit: r901334 - in /websites/staging/maven/trunk/content: ./
developers/website/deploy-component-reference-documentation.html
maven-site-1.0-site.jar
Author: buildbot
Date: Wed Mar 12 21:30:53 2014
New Revision: 901334
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 Mar 12 21:30:53 2014
@@ -1 +1 @@
-1576921
+1576924
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 Mar 12 21:30:53 2014
@@ -260,12 +260,12 @@ Hervé Boutemy" />
<li>build the reference documentation:
<div class="source">
<pre>mvn -Preporting site site:stage</pre></div>
-<p>Notice: <tt>site:stage</tt> is really necessary only for multi-modules components, but added inconditionnally in these instructions to keep them as straightforward as possible.</p></li>
+<p>Notice: <tt>site:stage</tt> is really necessary only for multi-modules components, but added unconditionally in these instructions to keep them as straightforward as possible.</p></li>
<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>mvn scm-publish:publish-scm</pre></div>
-<p>svnpubsub mecanism transfers svn production content to live production site</p></li></ol>
-<p><b>Notice</b>: to avoid published content do disappear when Maven main content si published (see <a href="./deploy-maven-website.html">documentation</a> for more details), check that the <tt>/xxx-archives</tt> path is properly declared in <a href="/extpaths.txt"><tt>extpaths.txt</tt></a>.</p></div>
+<p>svnpubsub mechanism transfers svn production content to live production site</p></li></ol>
+<p><b>Notice</b>: to avoid published content do disappear when Maven main content is published (see <a href="./deploy-maven-website.html">documentation</a> for more details), check that the <tt>/xxx-archives</tt> path is properly declared in <a href="/extpaths.txt"><tt>extpaths.txt</tt></a>.</p></div>
<div class="section">
<h3>Publishing versioned component reference documentation<a name="Publishing_versioned_component_reference_documentation"></a></h3>
<p>When doing a release, yyy-LATEST content staged in previous section needs:</p>
@@ -278,18 +278,18 @@ Hervé Boutemy" />
<div class="source">
<pre>SVNPUBSUB=https://svn.apache.org/repos/infra/websites/production/maven/content
-svn cp $SVNPUBSUB/xxx-archives/yyy-LATEST $SVNPUBSUB/xxx-archives/yyy-$version
+svn cp $SVNPUBSUB/xxx-archives/yyy-LATEST $SVNPUBSUB/xxx-archives/yyy-$version -m "Archive versioned site."
-svn rm $SVNPUBSUB/xxx/yyy
-svn cp $SVNPUBSUB/xxx-archives/yyy-$version $SVNPUBSUB/xxx/yyy</pre></div></li>
+svn rm $SVNPUBSUB/xxx/yyy -m "Remove old site."
+svn cp $SVNPUBSUB/xxx-archives/yyy-$version $SVNPUBSUB/xxx/yyy -m "Publish new site."</pre></div></li>
<li>Windows:
<div class="source">
<pre>set SVNPUBSUB=https://svn.apache.org/repos/infra/websites/production/maven/content
-svn cp %SVNPUBSUB%/xxx-archives/yyy-LATEST %SVNPUBSUB%/xxx-archives/yyy-$version
+svn cp %SVNPUBSUB%/xxx-archives/yyy-LATEST %SVNPUBSUB%/xxx-archives/yyy-$version -m "Archive versioned site."
-svn rm %SVNPUBSUB%/xxx/yyy
-svn cp %SVNPUBSUB%/xxx-archives/yyy-$version %SVNPUBSUB%/xxx/yyy</pre></div></li></ul>
+svn rm %SVNPUBSUB%/xxx/yyy -m "Remove old site."
+svn cp %SVNPUBSUB%/xxx-archives/yyy-$version %SVNPUBSUB%/xxx/yyy -m "Publish new site."</pre></div></li></ul>
<p>or with <a class="externalLink" href="http://svnbook.red-bean.com/en/1.8/svn.ref.svnmucc.re.html"><tt>svnmucc</tt> command</a>:</p>
<div class="source">
<pre>svnmucc -m "Publish yyy $version documentation" \
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.