Author: buildbot
Date: Mon Mar 12 02:52:25 2012
New Revision: 808299

Log:
Staging update by buildbot for maventest

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

Propchange: websites/staging/maventest/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Mar 12 02:52:25 2012
@@ -1 +1 @@
-1299536
+1299539

Modified: 
websites/staging/maventest/trunk/content/developers/release/maven-plugin-release.html
==============================================================================
--- 
websites/staging/maventest/trunk/content/developers/release/maven-plugin-release.html
 (original)
+++ 
websites/staging/maventest/trunk/content/developers/release/maven-plugin-release.html
 Mon Mar 12 02:52:25 2012
@@ -224,8 +224,8 @@ Hervé Boutemy" />
         <!-- 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 will be configured (TODO) to publish the 
documentation in Apache svn 
https://svn.apache.org/repos/infra/websites/production/maventest/latest 
(directory name to be discussed to match the intent).</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/checkout
 mvn site-deploy -Preporting
 svn cp 
https://svn.apache.org/repos/infra/websites/production/maventest/latest/plugins/maven-XXX-plugin
 \
-       
https://svn.apache.org/repos/infra/websites/production/maventest/content/plugins/maven-XXX-plugin-Y.Z</pre></div><p><b>Note:</b>
 You should verify the deployment of the site on the Maven website (you need to 
wait <a class="externalLink" 
href="http://www.apache.org/dev/cms.html#svnpubsub";>snvpubsub</a>), which 
should be a matter of seconds.</p><div 
class="source"><pre>http://maven.apache.org/plugins/maven-XXX-plugin-Y.Z/</pre></div></li><li>declare
 the directory in <a class="externalLink" 
href="http://maventest.apache.org/extpaths.txt";>extpaths.txt</a> using the CMS, 
through the bookmarklet.</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>TODO: make choice 
between multiple solutions:</p><ol style="list-style-type: lower-alpha"><li>svn 
copy<div class="source"><pre>svnmucc -U 
https://svn.apache.org/repos/infra/websites/production/mav
 entest/content/plugins \
-       rm maven-XXX-plugin cp maven-XXX-plugin-Y.Z 
maven-XXX-plugin</pre></div></li><li>change symlink: TODO find an easy way to 
change a symlink created in svn, like 
https://svn.apache.org/repos/infra/websites/production/maventest/content/ant-tasks</li></ol></div><div
 class="section"><h3>Updating the Maven site<a 
name="Updating_the_Maven_site"></a></h3><p>Use the CMS to update <a 
class="externalLink" href="http://maventest.apache.org/plugins/";>/plugins/</a> 
page, made easy with the bookmarklet.</p></div></div>
+       
https://svn.apache.org/repos/infra/websites/production/maventest/content/plugins/maven-XXX-plugin-Y.Z</pre></div><p><b>Note:</b>
 You should verify the deployment of the site on the Maven website (you need to 
wait <a class="externalLink" 
href="http://www.apache.org/dev/cms.html#svnpubsub";>snvpubsub</a>), which 
should be a matter of seconds.</p><div 
class="source"><pre>http://maven.apache.org/plugins/maven-XXX-plugin-Y.Z/</pre></div></li><li>declare
 the directory in <a href="/extpaths.txt">extpaths.txt</a> using the CMS, 
through the bookmarklet.</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>TODO: make choice 
between multiple solutions:</p><ol style="list-style-type: lower-alpha"><li>svn 
copy<div class="source"><pre>svnmucc -U 
https://svn.apache.org/repos/infra/websites/production/maventest/content/plugins
 \
+       rm maven-XXX-plugin cp maven-XXX-plugin-Y.Z 
maven-XXX-plugin</pre></div></li><li>change symlink: TODO find an easy way to 
change a symlink created in svn, like 
https://svn.apache.org/repos/infra/websites/production/maventest/content/ant-tasks</li></ol></div><div
 class="section"><h3>Updating the Maven site<a 
name="Updating_the_Maven_site"></a></h3><p>Use the CMS to update <a 
href="/plugins/">the plugins page</a>, made easy with the 
bookmarklet.</p></div></div>
       </div>
     </div>
     <div class="clear">


Reply via email to