svn commit: r843283 - in /websites/staging/maven/trunk/content: ./ developers/release/maven-plugin-release.html maven-site-1.0-site.jar

[bu...@apache.org]

Author: buildbot
Date: Thu Dec 20 21:56:04 2012
New Revision: 843283

Log:
Staging update by buildbot for maven

Modified:
    websites/staging/maven/trunk/content/   (props changed)
    websites/staging/maven/trunk/content/developers/release/maven-plugin-release.html
    websites/staging/maven/trunk/content/maven-site-1.0-site.jar

Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Dec 20 21:56:04 2012
@@ -1 +1 @@
-1424724
+1424727

Modified: websites/staging/maven/trunk/content/developers/release/maven-plugin-release.html
==============================================================================
--- websites/staging/maven/trunk/content/developers/release/maven-plugin-release.html (original)
+++ websites/staging/maven/trunk/content/developers/release/maven-plugin-release.html Thu Dec 20 21:56:04 2012
@@ -229,8 +229,8 @@
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><div class="section"><h2>Releasing A Maven Plugin<a name="Releasing_A_Maven_Plugin"></a></h2><p>Rele
 asing a Maven plugin is much the same as any other Maven project. The following guide walks through most of the steps:</p><ul><li><a href="./maven-project-release-procedure.html"> Maven Project Common Release procedure</a></li></ul><p>Note that plugins have particular conventions for deploying the project site. When encountered in the release process above, perform the following steps:</p><div class="section"><h3>Staging the latest documentation<a name="Staging_the_latest_documentation"></a></h3><p><b>Due to svnpubsub/CMS this documentation may be not up to date</b></p><p>Once the release is prepared, but before the release vote, the site needs to be staged.</p><p>The plugin parent POM is configured to stage the documentation in a &quot;versioned&quot; directory such as <tt>/plugins-archives/maven-XXX-plugin-Y.Z</tt>.</p><ol style="list-style-type: decimal"><li>Stage the documentation for the current release version (not the new snapshot).<div class="source"><pre>cd target/c
 heckout
-mvn site site:deploy -Preporting</pre></div><p><b>Note:</b> You should verify the deployment of the site on the Maven website.</p><div class="source"><pre>http://maven.apache.org/plugins-archives/maven-XXX-plugin-Y.Z/</pre></div></li></ol></div><div class="section"><h3>Deploying the release website<a name="Deploying_the_release_website"></a></h3><p>After the release has passed, the site needs to be uploaded.</p><p><b>Note:</b> 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 <tt>target/checkout</tt>)</p><div class="source"><pre>cd target/checkout
+        <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><div class="section"><h2>Releasing A Maven Plugin<a name="Releasing_A_Maven_Plugin"></a></h2><p>Rele
 asing a Maven plugin is much the same as any other Maven project. The following guide walks through most of the steps:</p><ul><li><a href="./maven-project-release-procedure.html"> Maven Project Common Release procedure</a></li></ul><p>Note that plugins have particular conventions for deploying the project site. When encountered in the release process above, perform the following steps:</p><div class="section"><h3>Staging the latest documentation<a name="Staging_the_latest_documentation"></a></h3><p>Once the release is prepared, but before the release vote, the site needs to be staged.</p><p>The plugin parent POM is configured to stage the documentation in a &quot;versioned&quot; directory such as <tt>/plugins-archives/maven-XXX-plugin-Y.Z</tt>.</p><p>Stage the documentation for the current release version (not the new snapshot).</p><div class="source"><pre>cd target/checkout
+mvn site site:deploy -Preporting</pre></div><p><b>Note:</b> You should verify the deployment of the site on the Maven website.</p><div class="source"><pre>http://maven.apache.org/plugins-archives/maven-XXX-plugin-Y.Z/</pre></div></div><div class="section"><h3>Deploying the release website<a name="Deploying_the_release_website"></a></h3><p>After the release has passed, the site needs to be uploaded.</p><p><b>Note:</b> 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 <tt>target/checkout</tt>)</p><div class="source"><pre>cd target/checkout
 mvn site-deploy -Preporting -Psite-release</pre></div><p>To review the site, wait for the files to arrive at</p><div class="source"><pre>http://maven.apache.org/plugins/maven-XXX-plugin/</pre></div></div><div class="section"><h3>Updating the Maven site<a name="Updating_the_Maven_site"></a></h3><p>See <a href="../website/deploy-maven-website.html">Deploy Maven website</a></p><p>Update the version number for the plugin on the <tt>src/site/apt/plugins/index.apt</tt> page.</p></div></div>
       </div>
     </div>

Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.