maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r889489 - in /websites/staging/maven/trunk/content: ./ developers/release/maven-project-release-procedure.html developers/release/parent-pom-release.html developers/release/releasing.html maven-site-1.0-site.jar
Date Sat, 07 Dec 2013 16:51:57 GMT
Author: buildbot
Date: Sat Dec  7 16:51:57 2013
New Revision: 889489

Staging update by buildbot for maven

    websites/staging/maven/trunk/content/   (props changed)

Propchange: websites/staging/maven/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Sat Dec  7 16:51:57 2013
@@ -1 +1 @@

Modified: websites/staging/maven/trunk/content/developers/release/maven-project-release-procedure.html
--- websites/staging/maven/trunk/content/developers/release/maven-project-release-procedure.html
+++ websites/staging/maven/trunk/content/developers/release/maven-project-release-procedure.html
Sat Dec  7 16:51:57 2013
@@ -268,8 +268,7 @@
 <h3>Stage the Release<a name="Stage_the_Release"></a></h3>
 <ol style="list-style-type: decimal">
 <li>Follow the release preparation, staging and closing the repository steps outlined
in <a class="externalLink" href="">Staging
a Maven release</a>. </li>
-<li>Stage the latest documentation
-<p>If your project uses Maven to generate documentation and it is not included as part
of the release process, stage it now for inclusion in the release vote. For Maven projects,
refer to the specific instructions for the project you are releasing.</p></li></ol></div>
+<li>Stage the latest documentation as explained in <a href="../website/deploy-component-reference-documentation.html">deploying
Maven components reference documentation</a>.</li></ol></div>
 <div class="section">
 <h3>Call the vote<a name="Call_the_vote"></a></h3>
 <p>Propose a vote on the dev list with the closed issues, the issues left, the staging
repository and the staging site. For instance:</p>

Modified: websites/staging/maven/trunk/content/developers/release/parent-pom-release.html
--- websites/staging/maven/trunk/content/developers/release/parent-pom-release.html (original)
+++ websites/staging/maven/trunk/content/developers/release/parent-pom-release.html Sat Dec
 7 16:51:57 2013
@@ -14,7 +14,7 @@
     <link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
         <meta name="author" content="Hervé Boutemy
 Dennis Lundberg" />
-        <meta name="Date-Creation-yyyymmdd" content="20121104" />
+        <meta name="Date-Creation-yyyymmdd" content="20131207" />
     <meta name="Date-Revision-yyyymmdd" content="20131207" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -244,7 +244,7 @@ Dennis Lundberg" />
 <p>Releasing a Parent POM is much the same as any other Maven project. The following
guide walks through most of the steps:</p>
 <li><a href="./maven-project-release-procedure.html"> Maven Project Common Release
-<p>Note that Parent POMs have particular conventions for managing and deploying the
project site.</p>
+<p>Note that Parent POMs have particular conventions for managing and deploying the
 <div class="section">
 <h3>Rationale<a name="Rationale"></a></h3>
 <p>To be able to publish a documentation for the parent POM without affecting released
POM and <tt>site.xml</tt>, parent POM projects have a specific structure, with
the addition of <tt>site-pom.xml</tt> and <tt>src/site-docs</tt> provide
<tt>mvn -f site-pom.xml site</tt>:</p>
@@ -269,22 +269,12 @@ Dennis Lundberg" />
 <p>Once these modifications are done, you can follow standard staging steps taking
care to use the <tt>site-pom.xml</tt> POM, with <tt>mvn -f site-pom.xml
...</tt> command, each time the parent POM's site is generated.</p></div>
 <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
-<p>The parent POMs are configured to stage the documentation in a &quot;versioned&quot;
directory such as <tt>/pom/XXX-Y</tt>.</p>
-<ol style="list-style-type: decimal">
-<li>Stage the documentation for the current release version (not the new snapshot).
+<p>Instructions for staging latest documentation are the same as <a href="../website/deploy-component-reference-documentation.html">standard
component</a>, with the addition of <tt>-f site-pom.xml</tt>.</p>
+<p>Then the only difference is with commands to stage the site:</p>
 <div class="source">
 <pre>cd target/checkout
-mvn -f site-pom.xml site site:stage-deploy</pre></div>
-<p><b>Note:</b> It requires Maven 2.1.0 or higher to successfully deploy
to <tt></tt> via SSH. Older Maven versions will fail due to <tt>com.jcraft.jsch.JSchException:
Algorithm negotiation fail</tt>.</p>
-<p><b>Note:</b> You should verify the deployment of the site on the Maven
website (you need to wait <a class="externalLink" href="">the
-<div class="source">
-<li>Verify/change folder permissions to 0775 and files permissions to 0664. Log on
to <tt></tt> and change to the directory above the staging directory.
Then run these commands:
-<div class="source">
-<pre>cd /www/
-find . -type d -exec chmod a+rx,g+w {} \;
-find . -type f -exec chmod 664 {} \;</pre></div></li></ol></div>
+mvn -f site-pom.xml site
+mvn -f site-pom.xml scm-publish:publish-scm</pre></div></div>
 <div class="section">
 <h3>Call the vote<a name="Call_the_vote"></a></h3>
 <p>In the vote, instead of providing links to JIRA, the parent POMs should include
a link to the SVN changes since the last release:</p>
@@ -296,26 +286,7 @@ Changes since the last release:;TAG&gt;/pom.xml?r1=HEAD&amp;r2=&lt;REVISION-OF-LAST-RELEASE&gt;&amp;diff_format=h
 Staging repo:
-<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 -f site-pom.xml site-deploy</pre></div>
-<p><b>Note:</b> 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
<a class="externalLink" href=";framed=y">;framed=y</a></p>
-<p>To review the site, wait for the files to arrive at</p>
-<div class="source">
-<p>The wait is necessary to allow the site to be <a class="externalLink" href="">rsync'ed
into production</a>.</p></div>
-<div class="section">
-<h3>Updating the Maven site<a name="Updating_the_Maven_site"></a></h3>
-<p>Check out the Maven site project from <tt></tt>
or pull the latest changes if already checked out.</p>
-<p>Update the version number and release date for the parent POM on the <tt>src/site/apt/pom/index.apt</tt>
-<p>Commit your changes and then deploy the site.</p>
-<div class="source">
-<pre>mvn clean site-deploy</pre></div></div></div>
     <div class="clear">

Modified: websites/staging/maven/trunk/content/developers/release/releasing.html
--- websites/staging/maven/trunk/content/developers/release/releasing.html (original)
+++ websites/staging/maven/trunk/content/developers/release/releasing.html Sat Dec  7 16:51:57
@@ -240,11 +240,9 @@
       <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 --><!--  --><!--
--><!--  --><!-- 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 Project<a name="Releasing_A_Maven_Project"></a></h2>
-<p>What follows is a description of releasing a Maven project to a staging repository,
whereupon it is scrutinized by the community, approved, and transferred to a production repository.</p>
-<p>The steps involved are similar for any Apache project, with more specifics for Maven
plugins, shared libraries, and Maven itself. The steps involved, and the relevant documents
for each, are listed below.</p>
+<p>What follows is a description of releasing a Maven project to a staging repository
and its documentation, whereupon it is scrutinized by the community, approved, and transferred
to a production repository.</p>
+<p>The steps involved are similar for any Apache project, with more specifics for parent
POMs and Maven itself. The steps involved, and the relevant documents for each, are listed
below.</p><!-- nothing specific: normal component  * {{{./maven-plugin-release.html}
Releasing a Maven plugin project}} --><!-- nothing specific: normal component * {{{./maven-shared-release.html}
Releasing a Maven shared component or subproject}} -->
-<li><a href="./maven-plugin-release.html"> Releasing a Maven plugin project</a></li>
-<li><a href="./maven-shared-release.html"> Releasing a Maven shared component
or subproject</a></li>
 <li><a href="./maven-core-release.html"> Releasing Maven Core</a></li>
 <li><a href="./parent-pom-release.html"> Releasing a parent POM</a></li></ul>
 <p>The above links all provide specific information for those types of releases, but
they all refer back to the common documentation:</p>

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

View raw message