Differences between revisions 1 and 2
Revision 1 as of 2010-12-22 15:12:02
Size: 1544
Comment:
Revision 2 as of 2013-05-31 15:12:29
Size: 1626
Comment: Outdated
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

''' WARNING: THESE INSTRUCTIONS ARE OUTDATED - THE SITE NOW USES SVNPUBSUB '''

HttpComponents Component Web Site

WARNING: THESE INSTRUCTIONS ARE OUTDATED - THE SITE NOW USES SVNPUBSUB

Generate content

Run the following command to generate the site content locally. Please note this process requires a valid Clover2 license.

ASF committers can obtain a copy of Clover2 license donated to the ASF at this location

mvn docbkx:generate-pdf docbkx:generate-html javadoc:javadoc site -Dmaven.clover.licenseLocation=<full-path>/clover.license 

Review and adjust the content if necessary.

Deploy content

Deploy site content to people.apache.org

mvn site-deploy -Dmaven.clover.licenseLocation=<full-path>/clover.license 

Manual adjustments

Log to people.apache.org and navigate to the web content staging directory

cd /www/hc.apache.org/

Move component content to a directory with a unique name (usually containing the component version)

mv httpcomponents-core httpcomponents-core-4.1.1

Change the symbolic link for the actual DEV or GA release to point at the component directory.

rm httpcomponents-core-ga
ln -s httpcomponents-core-4.1.1 httpcomponents-core-ga 

rm httpcomponents-core-dev
ln -s httpcomponents-core-4.2-snapshot httpcomponents-core-dev 

Verify content

It may take several hours for the new content in the staging directory to get propagated to the productive web server. Verify that the site content is rendered correctly once it becomes available.

WebSite/ComponentSite (last edited 2013-05-31 15:12:29 by SebastianBazley)