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 2013/09/29 21:11:22 UTC

svn commit: r880388 - in /websites/staging/maven/trunk/content: ./ developers/website/deploy-maven-website.html maven-site-1.0-site.jar

Author: buildbot
Date: Sun Sep 29 19:11:22 2013
New Revision: 880388

Log:
Staging update by buildbot for maven

Modified:
    websites/staging/maven/trunk/content/   (props changed)
    websites/staging/maven/trunk/content/developers/website/deploy-maven-website.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 Sun Sep 29 19:11:22 2013
@@ -1 +1 @@
-1527387
+1527388

Modified: websites/staging/maven/trunk/content/developers/website/deploy-maven-website.html
==============================================================================
--- websites/staging/maven/trunk/content/developers/website/deploy-maven-website.html (original)
+++ websites/staging/maven/trunk/content/developers/website/deploy-maven-website.html Sun Sep 29 19:11:22 2013
@@ -277,9 +277,9 @@ Hervé Boutemy" />
 <h2>How Doxia website publication works<a name="How_Doxia_website_publication_works"></a></h2>
 <p>Doxia uses the exact same mecanisms:</p>
 <ul>
-<li>you can edit <a class="externalLink" href="https://svn.apache.org/repos/asf/maven/doxia/site/trunk}svn source tree">https://svn.apache.org/repos/asf/maven/doxia/site/trunk}svn source tree</a> either locally or through <a class="externalLink" href="https://cms.apache.org/maven-doxia/}CMS UI">https://cms.apache.org/maven-doxia/}CMS UI</a>,</li>
-<li><a class="externalLink" href="http://ci.apache.org/builders/maven-doxia-site-staging}a Buildbot job">http://ci.apache.org/builders/maven-doxia-site-staging}a Buildbot job</a> builds the site and updates <a class="externalLink" href="https://svn.apache.org/repos/infra/websites/staging/maven-doxia/trunk/content/}website staging svn area">https://svn.apache.org/repos/infra/websites/staging/maven-doxia/trunk/content/}website staging svn area</a>,</li>
-<li>svnpubsub published to <a class="externalLink" href="http://maven-doxia.staging.apache.org}live staging site">http://maven-doxia.staging.apache.org}live staging site</a>,</li>
+<li>you can edit <a class="externalLink" href="https://svn.apache.org/repos/asf/maven/doxia/site/trunk">svn source tree</a> either locally or through <a class="externalLink" href="https://cms.apache.org/maven-doxia/">CMS UI</a>,</li>
+<li><a class="externalLink" href="http://ci.apache.org/builders/maven-doxia-site-staging">a Buildbot job</a> builds the site and updates <a class="externalLink" href="https://svn.apache.org/repos/infra/websites/staging/maven-doxia/trunk/content/">website staging svn area</a>,</li>
+<li>svnpubsub published to <a class="externalLink" href="http://maven-doxia.staging.apache.org">live staging site</a>,</li>
 <li>if everything is good, <b>publish modifications</b> using <a class="externalLink" href="https://cms.apache.org/maven-doxia/publish">CMS publish</a> action,</li>
 <li>CMS copies CMS staging svn area content to <a class="externalLink" href="https://svn.apache.org/repos/infra/websites/production/maven-doxia/content/">website production svn area</a>,</li>
 <li>svnpubsub mecanism transfers svn production content to live production site: <a class="externalLink" href="http://maven.apache.org/doxia">http://maven.apache.org/doxia</a>, with its <a class="externalLink" href="http://maven.apache.org/doxia/extpaths.txt"><tt>extpaths.txt</tt></a></li></ul></div>

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