You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2013/09/22 17:45:45 UTC
svn commit: r1525380 -
/maven/site/trunk/content/apt/developers/website/deploy-maven-website.apt
Author: hboutemy
Date: Sun Sep 22 15:45:45 2013
New Revision: 1525380
URL: http://svn.apache.org/r1525380
Log:
fixed website svn production urls: these one don't have "trunk" in url
Modified:
maven/site/trunk/content/apt/developers/website/deploy-maven-website.apt
Modified: maven/site/trunk/content/apt/developers/website/deploy-maven-website.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/apt/developers/website/deploy-maven-website.apt?rev=1525380&r1=1525379&r2=1525380&view=diff
==============================================================================
--- maven/site/trunk/content/apt/developers/website/deploy-maven-website.apt (original)
+++ maven/site/trunk/content/apt/developers/website/deploy-maven-website.apt Sun Sep 22 15:45:45 2013
@@ -71,7 +71,7 @@ How website publication works
[[3]] if everything is good, publish modifications using CMS publish: {{https://cms.apache.org/maven/publish}}
- [[1]] CMS copies staging svn area content to production svn area: {{https://svn.apache.org/repos/infra/websites/production/maven/trunk/content/}},
+ [[1]] CMS copies staging svn area content to production svn area: {{https://svn.apache.org/repos/infra/websites/production/maven/content/}},
[[2]] as previous operation will delete content not built from website source, CMS re-adds content identified in {{{http://maven.apache.org/extpaths.txt}<<<extpaths.txt>>>}},
@@ -93,7 +93,7 @@ How website publication works
* CMS publish: {{https://cms.apache.org/maven-doxia/publish}}
- * production svn area: {{https://svn.apache.org/repos/infra/websites/production/maven-doxia/trunk/content/}}
+ * production svn area: {{https://svn.apache.org/repos/infra/websites/production/maven-doxia/content/}}
* live production site: {{http://maven.apache.org/doxia}}
@@ -135,6 +135,7 @@ mvn scm-publish:publish-scm
svnpubsub mecanism transfers svn production content to live production site
[]
+
[]
When doing a release, previous xxx-LATEST content needs to be archived to versioned directory and replace current content (TODO: explanations).