Index: pom.xml =================================================================== --- pom.xml (revision 1434461) +++ pom.xml (working copy) @@ -32,7 +32,7 @@ org.apache apache - 8 + 12 @@ -747,6 +747,7 @@ + org.apache.maven.plugins maven-resources-plugin ${maven.resources.plugin.version} @@ -886,7 +887,7 @@ 1.3.9-1 3.1 2.9 - 2.5 + 2.6 /usr /etc/hbase @@ -1701,9 +1702,10 @@ - - apache.website - scp://people.apache.org/www/hbase.apache.org/ - + + hbase.apache.org + HBase Website at hbase.apache.org + file:///tmp + Index: src/docbkx/developer.xml =================================================================== --- src/docbkx/developer.xml (revision 1434414) +++ src/docbkx/developer.xml (working copy) @@ -335,12 +335,15 @@ Publishing hbase.apache.org As of INFRA-5680 Migrate apache hbase website, to publish the website, build it, and then deploy it over a checkout of https://svn.apache.org/repos/asf/hbase/hbase.apache.org/trunk, - and then check it in. For example, if trunk is checkout out at /Users/stack/checkouts/hbase + and then check it in. For example, if trunk is checked out out at /Users/stack/checkouts/trunk and hbase.apache.org is checked out at /Users/stack/checkouts/hbase.apache.org/trunk, to update the site, do the following: # Build the site and deploy it to the checked out directory - $ MAVEN_OPTS=" -Xmx3g" mvn site site:stage -DskipTests -DstagingDirectory="/Users/stack/checkouts/hbase.apache.org/trunk" + # Getting the javadoc into site is a little tricky. You have to build it independent, then + # 'aggregate' it at top-level so the pre-site site lifecycle step can find it; that is + # what the javadoc:javadoc and javadoc:aggregate is about. + $ MAVEN_OPTS=" -Xmx3g" mvn clean -DskipTests javadoc:javadoc javadoc:aggregate site site:stage -DstagingDirectory=/Users/stack/checkouts/hbase.apache.org/trunk # Check the deployed site by viewing in a brower. # If all is good, commit it and it will show up at http://hbase.apache.org #