svn commit: r1465231 - /commons/cms-site/trunk/content/xdoc/releases/publish-site.xml

[ol...@apache.org]

Author: olamy
Date: Sat Apr  6 12:05:11 2013
New Revision: 1465231

URL: http://svn.apache.org/r1465231
Log:
publishing site documentation has been moved.

Modified:
    commons/cms-site/trunk/content/xdoc/releases/publish-site.xml

Modified: commons/cms-site/trunk/content/xdoc/releases/publish-site.xml
URL: http://svn.apache.org/viewvc/commons/cms-site/trunk/content/xdoc/releases/publish-site.xml?rev=1465231&r1=1465230&r2=1465231&view=diff
==============================================================================
--- commons/cms-site/trunk/content/xdoc/releases/publish-site.xml (original)
+++ commons/cms-site/trunk/content/xdoc/releases/publish-site.xml Sat Apr  6 12:05:11 2013
@@ -27,44 +27,9 @@
 <section name='Publishing The Website'>
 
   <subsection name="Update Component Website">
-    <strong>Publish Updated Website</strong>
-    <p>
-    Run the following to deploy the new component website:
-    <pre>
-      mvn site:deploy
-    </pre>
-    </p>
-    <p>
-    On people.apache.org, verify that the directory has been updated, and that the
-    file and directory permissions are correct (readable by all, not writeable by
-    world, but group writeable).
-    </p>
-    <p>
-    Note that the files are transferred to the real web site only every
-    few hours, so it may be a while before you see your changes appear. However if
-    you set your webbrowser's HTTP proxy to 140.211.11.10 port 80 and access
-    http://commons.apache.org/ you should be able to see the changes immediately.
-    </p>
-    <strong>Perform Manual Fixups (if any)</strong>
-    <p>
-    It is quite nice for a component website to provide not just the latest javadocs and
-    release notes, but also links to this information for previous releases. However Maven
-    doesn't provide any way to do this. The usual solution is therefore for the component
-    to arrange for its generated website to have some navbar links that point to somewhere
-    that doesn't exist (at least not created by Maven), then manually put the missing info
-    at the needed location after "maven site:deploy" has been run. If the component you
-    are deploying has done such tricks, then you need to do the manual fixups now.
-    </p>
     <p>
-    As an example, the foo component's website might have links for "1.1 release notes"
-    and "1.1 javadoc" that point to "release11/RELEASE-NOTES.txt" and "release11/api";
-    in that case you'll need to create that release11 directory and install the old
-    release notes and javadoc there. 
-    </p>
-    <p>
-    Note that "maven site:deploy" will not delete any extra directories or files that were
-    already there, so if there was a "release10" directory that is no longer referenced
-    from the new website then you should delete that old directory.
+    <strong>Publish Updated Website</strong>
+    <strong>Due to the use of svnpubsub system please refer to pages located here <a href="http://commons.staging.apache.org/releases/publish-site.html">http://commons.staging.apache.org/releases/publish-site.html</a></strong>
     </p>
   </subsection>