svn commit: r1424724 - /maven/site/trunk/content/apt/developers/release/maven-plugin-release.apt

[ol...@apache.org]

Author: olamy
Date: Thu Dec 20 21:52:43 2012
New Revision: 1424724

URL: http://svn.apache.org/viewvc?rev=1424724&view=rev
Log:
update documentation due to cms use

Modified:
    maven/site/trunk/content/apt/developers/release/maven-plugin-release.apt

Modified: maven/site/trunk/content/apt/developers/release/maven-plugin-release.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/apt/developers/release/maven-plugin-release.apt?rev=1424724&r1=1424723&r2=1424724&view=diff
==============================================================================
--- maven/site/trunk/content/apt/developers/release/maven-plugin-release.apt (original)
+++ maven/site/trunk/content/apt/developers/release/maven-plugin-release.apt Thu Dec 20 21:52:43 2012
@@ -40,44 +40,21 @@ Releasing A Maven Plugin
   Once the release is prepared, but before the release vote, the site needs to be staged.
 
   The plugin parent POM is configured to stage the documentation in a "versioned" directory
-  such as <<</plugins/maven-XXX-plugin-Y.Z>>>.
+  such as <<</plugins-archives/maven-XXX-plugin-Y.Z>>>.
 
    [[1]] Stage the documentation for the current release version (not the new snapshot).
 
 +------+
 cd target/checkout
-mvn site site:stage-deploy -Preporting
+mvn site site:deploy -Preporting
 +------+
 
-   <<Note:>> It requires Maven 2.1.0 or higher to successfully deploy to <<<people.apache.org>>> via SSH. Older Maven
-   versions will fail due to <<<com.jcraft.jsch.JSchException: Algorithm negotiation fail>>>.
-
-   <<Note:>> You should verify the deployment of the site on the Maven website
-   (you need to wait {{{http://www.apache.org/dev/project-site.html}the sync}}).
+   <<Note:>> You should verify the deployment of the site on the Maven website.
 
 +-----+
-http://maven.apache.org/plugins/maven-XXX-plugin-Y.Z/
+http://maven.apache.org/plugins-archives/maven-XXX-plugin-Y.Z/
 +-----+
 
-   Some developers have {{{http://www.nabble.com/site%3Astage-deploy-asks-for-a-password--tt15582961s177.html}
-   reported problems}} with the <<<site:stage-deploy>>> goal.  In that case, you can stage the site locally and
-   upload it manually:
-
-+------+
-mvn site site:stage -Preporting
-scp -r target/staging/people.apache.org/www/maven.apache.org/plugins/maven-XXX-plugin YOUR_APACHE_USERNAME@people.apache.org:/www/maven.apache.org/plugins/maven-XXX-plugin-Y.Z
-+------+
-
-   [[2]] Verify/change folder permissions to 0775 and files permissions to 0664. Log on to <<<people.apache.org>>> and
-   change to the directory above the staging directory.
-   Then run these commands:
-
-+------+
-cd /www/maven.apache.org/plugins
-find . -type d -exec chmod a+rx,g+w {} \;
-find . -type f -exec chmod 664 {} \;
-+------+
-
 * Deploying the release website
 
   After the release has passed, the site needs to be uploaded.
@@ -87,30 +64,18 @@ find . -type f -exec chmod 664 {} \;
 
 +-----+
 cd target/checkout
-mvn site-deploy -Preporting
+mvn site-deploy -Preporting -Psite-release
 +-----+
 
-  <<Note:>> You can not just copy the documentation from the staging site above into the released documentation as the links are not identical.
-  See the email thread {{http://www.nabble.com/forum/ViewPost.jtp?post=24018250&framed=y}}
-
  To review the site, wait for the files to arrive at
 
 +-----+
 http://maven.apache.org/plugins/maven-XXX-plugin/
 +-----+
 
- The wait is necessary to allow the site to be
- {{{http://www.apache.org/dev/project-site.html}rsync'ed into production}}.
-
 * Updating the Maven site
 
- Check out the maven site project from <<<https://svn.apache.org/repos/asf/maven/site/trunk>>> or pull the latest
- changes if already checked out.
+ See {{{../website/deploy-maven-website.html}Deploy Maven website}}
 
  Update the version number for the plugin on the <<<src/site/apt/plugins/index.apt>>> page.
 
- Commit your changes and then deploy the site.
-
-+-----+
-mvn clean site-deploy
-+-----+