Author: olamy
Date: Sat Feb 23 22:33:01 2013
New Revision: 1449419
URL: http://svn.apache.org/r1449419
Log:
fix doc for shared component release
Modified:
maven/site/trunk/content/apt/developers/release/maven-shared-release.apt
Modified:
maven/site/trunk/content/apt/developers/release/maven-shared-release.apt
URL:
http://svn.apache.org/viewvc/maven/site/trunk/content/apt/developers/release/maven-shared-release.apt?rev=1449419&r1=1449418&r2=1449419&view=diff
==============================================================================
--- maven/site/trunk/content/apt/developers/release/maven-shared-release.apt
(original)
+++ maven/site/trunk/content/apt/developers/release/maven-shared-release.apt
Sat Feb 23 22:33:01 2013
@@ -4,7 +4,7 @@
Jason van Zyl
bimargulies
-----
- 2011-06-19
+ 2013-02-23
-----
~~ Licensed to the Apache Software Foundation (ASF) under one
@@ -45,38 +45,10 @@ Releasing A Maven Shared Component
+------+
cd target/checkout
-mvn site site:stage-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}}).
-
-+-----+
-http://maven.apache.org/shared/maven-XXX-Y.Z/
+mvn site site:deploy -Preporting
+-----+
- Some developers have
{{{http://www.nabble.com/site%3Astage-deploy-asks-for-a-password--tt15582961s177.html}
- reported problems}} with the <<<site:stage-deploy>>> goal. See the
discussion of settings.xml below
- for one possible solution. If that doesn't work, 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/shared/maven-XXX
[email protected]:/www/maven.apache.org/shared/maven-XXX-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/shared
-find . -type d -exec chmod a+rx,g+w {} \;
-find . -type f -exec chmod 664 {} \;
-+------+
+ deployed to http://maven.apache.org/shared-archives/maven-XXX-Y.Z/
* Deploying the release website
@@ -85,47 +57,23 @@ find . -type f -exec chmod 664 {} \;
<<Note:>> Be sure to generate and deploy the site using the same version of
the release. Typically, you need to check
out the tag (or go to <<<target/checkout>>>)
- You will need to have your people.apache.org credentials in your
settings.xml, and you may have to
- explicitly specify the server ID on the command line to persuade maven to use
them.
+ +-----+
+cd target/checkout
+mvn site-deploy -Preporting -Psite-release
++-----+
- Due to an apparent problem with the site plugin, passwords don't work
reliably for this purpose. SSH keys do.
- As per the doc for settings.xml, Maven ignores a private key in settings.xml
if it sees a password. So, to
- deploy a site, you should make sure that your settings.xml contains something
like:
-
-+----------------+
- <server>
- <id>apache.website</id>
- <username>mortimerqsnerd</username>
- <privateKey>${user.home}/.ssh/id_rsa</privateKey>
- </server>
-+----------------+
+ Or
+-----+
-cd target/checkout
-mvn site-deploy -Preporting -DstagingRepositoryId=apache.website
+csvn rm
https://svn.apache.org/repos/infra/websites/production/maven/content/shared/maven-XXX
+svn cp
https://svn.apache.org/repos/infra/websites/production/maven/content/shared-archives/maven-XXX-Y.Z
\
+
https://svn.apache.org/repos/infra/websites/production/maven/content/plugins/maven-
+-----+
- <<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/shared/maven-XXX/
+-----+
- 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.
-
- Update the version number for the component on the
<<<src/site/apt/shared/index.apt>>> page.
-
- Commit your changes and then deploy the site.
-
-+-----+
-mvn clean site-deploy
-+-----+
+
\ No newline at end of file
