You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by bu...@apache.org on 2013/04/27 09:29:25 UTC
svn commit: r860084 [5/39] - in /websites/staging/maven/trunk/content: ./
background/ developers/ developers/conventions/ developers/release/
developers/website/ docs/2.0.1/ docs/2.0.10/ docs/2.0.11/ docs/2.0.2/
docs/2.0.3/ docs/2.0.4/ docs/2.0.5/ docs...
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 (original)
+++ websites/staging/maven/trunk/content/developers/release/maven-project-release-procedure.html Sat Apr 27 07:29:22 2013
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at Apr 23, 2013
+ | Generated by Apache Maven Doxia at Apr 27, 2013
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -14,7 +14,7 @@
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Jason van Zyl" />
<meta name="Date-Creation-yyyymmdd" content="20130306" />
- <meta name="Date-Revision-yyyymmdd" content="20130423" />
+ <meta name="Date-Revision-yyyymmdd" content="20130427" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -44,7 +44,7 @@
Releasing A Maven Project
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -232,7 +232,43 @@
</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>Performing a Maven Project Release<a name="Performing_a_Maven_Project_Relea
se"></a></h2><p>This document covers the common release procedures used by the Maven team to perform releases.</p><div class="section"><h3><a name="Prerequisites">Prerequisites</a></h3><p>Be sure that:</p><ul><li>you have a Subversion 1.5+ client installed and on your shell's path. See <a class="externalLink" href="http://subversion.apache.org/">http://subversion.apache.org/</a>.</li><li>you have JDK 5 installed and on your shell's path.</li><li>if you receive an OutOfMemoryError during the build, make sure to have set the environment variable <tt>MAVEN_OPTS=-Xmx512m</tt></li><li>you must use Maven 2.2.1+, as Maven 2.1.0 and 2.2.0 produce incorrect GPG signatures and checksums respectively.</li><li>follow Apache environment configuration steps outlined at: <a class="externalLink" href="http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env">Publishing Maven Artifacts</a>.</li></ul></div><div class="section"><h3>Before you begin<a name="Before_you_begin"></a></h3><
p>If you started here, you may first want to review one of the following documents that cover the specifics of various types of releases we have in the Maven Project:</p><ul><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></div><div class="section"><h3>Consider updating the parent versions<a name="Consider_updating_the_parent_versions"></a></h3><p>If the item you are planning to release is not using the most recent version of its parent (see <a href="../../pom/">parent POMs</a> index), consider taking this opportunity to update to it.</p></div><div class="section"><h3>Make sure that site compilation and publication works<a name="Make_sure_that_site_compilation_and_publication_works"></a></h3><p>Pa
rticularly if you update the parent (but sometimes under other circumstances), the site compilation process may fail, or reveal a conspicuous error, or deploy to the wrong location. It is stressful and time-consuming to discover this *after* you stage a release and then try to follow the procedure to deploy the site for review. So you may find it more pleasant to check out the state of the site before you start.</p></div><div class="section"><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="http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven">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><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><div class="source"><pre>To: "Maven Developers List" <dev@maven.apache.org>
+ <!-- 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>Performing a Maven Project Release<a name="Performing_a_Maven_Project_Release"></a></h2>
+<p>This document covers the common release procedures used by the Maven team to perform releases.</p>
+<div class="section">
+<h3><a name="Prerequisites">Prerequisites</a></h3>
+<p>Be sure that:</p>
+<ul>
+<li>you have a Subversion 1.5+ client installed and on your shell's path. See <a class="externalLink" href="http://subversion.apache.org/">http://subversion.apache.org/</a>.</li>
+<li>you have JDK 5 installed and on your shell's path.</li>
+<li>if you receive an OutOfMemoryError during the build, make sure to have set the environment variable <tt>MAVEN_OPTS=-Xmx512m</tt></li>
+<li>you must use Maven 2.2.1+, as Maven 2.1.0 and 2.2.0 produce incorrect GPG signatures and checksums respectively.</li>
+<li>follow Apache environment configuration steps outlined at: <a class="externalLink" href="http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env">Publishing Maven Artifacts</a>.</li></ul></div>
+<div class="section">
+<h3>Before you begin<a name="Before_you_begin"></a></h3>
+<p>If you started here, you may first want to review one of the following documents that cover the specifics of various types of releases we have in the Maven Project:</p>
+<ul>
+<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></div>
+<div class="section">
+<h3>Consider updating the parent versions<a name="Consider_updating_the_parent_versions"></a></h3>
+<p>If the item you are planning to release is not using the most recent version of its parent (see <a href="../../pom/">parent POMs</a> index), consider taking this opportunity to update to it.</p></div>
+<div class="section">
+<h3>Make sure that site compilation and publication works<a name="Make_sure_that_site_compilation_and_publication_works"></a></h3>
+<p>Particularly if you update the parent (but sometimes under other circumstances), the site compilation process may fail, or reveal a conspicuous error, or deploy to the wrong location. It is stressful and time-consuming to discover this *after* you stage a release and then try to follow the procedure to deploy the site for review. So you may find it more pleasant to check out the state of the site before you start.</p></div>
+<div class="section">
+<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="http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven">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>
+<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>
+<div class="source">
+<pre>To: "Maven Developers List" <dev@maven.apache.org>
Subject: [VOTE] Release Maven XXX Plugin version Y.Z
Hi,
@@ -258,13 +294,24 @@ Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
-</pre></div><p>To get the JIRA release notes link, browse to the plugin's JIRA page, select the <i>Road Map</i> link, and use the link to <i>Release Notes</i> that is next to the version being released.</p><p>To get the list of issues left in JIRA, browse to the plugin's JIRA page, and from the <i>Preset Filters</i> on the right, use the link for <i>Outstanding</i> issues.</p></div><div class="section"><h3>Check the vote results<a name="Check_the_vote_results"></a></h3><p>Copied from <a class="externalLink" href="http://www.apache.org/foundation/voting.html">Votes on Package Releases</a>.</p><div class="source"><pre>Votes on whether a package is ready to be released follow a format similar to majority approval
+</pre></div>
+<p>To get the JIRA release notes link, browse to the plugin's JIRA page, select the <i>Road Map</i> link, and use the link to <i>Release Notes</i> that is next to the version being released.</p>
+<p>To get the list of issues left in JIRA, browse to the plugin's JIRA page, and from the <i>Preset Filters</i> on the right, use the link for <i>Outstanding</i> issues.</p></div>
+<div class="section">
+<h3>Check the vote results<a name="Check_the_vote_results"></a></h3>
+<p>Copied from <a class="externalLink" href="http://www.apache.org/foundation/voting.html">Votes on Package Releases</a>.</p>
+<div class="source">
+<pre>Votes on whether a package is ready to be released follow a format similar to majority approval
-- except that the decision is officially determined solely by whether at least three
+1 votes were registered. Releases may not be vetoed. Generally the community will table the
vote to release if anyone identifies serious problems, but in most cases the ultimate decision,
once three or more positive votes have been garnered, lies with the individual serving as
release manager. The specifics of the process may vary from project to project, but the
-'minimum of three +1 votes' rule is universal.</pre></div><p>The list of binding voters is available at <a class="externalLink" href="http://people.apache.org/committers-by-project.html#maven-pmc">http://people.apache.org/committers-by-project.html#maven-pmc</a> (or corresponding group for your project).</p><p>Once a vote is successful, post the result to the dev list and cc the PMC. For instance:</p><div class="source"><pre>To: "Maven Developers List" <dev@maven.apache.org>
+'minimum of three +1 votes' rule is universal.</pre></div>
+<p>The list of binding voters is available at <a class="externalLink" href="http://people.apache.org/committers-by-project.html#maven-pmc">http://people.apache.org/committers-by-project.html#maven-pmc</a> (or corresponding group for your project).</p>
+<p>Once a vote is successful, post the result to the dev list and cc the PMC. For instance:</p>
+<div class="source">
+<pre>To: "Maven Developers List" <dev@maven.apache.org>
CC: "Maven Project Management Committee List" <private@maven.apache.org>
Subject: [RESULT] [VOTE] Release Maven XXX Plugin version Y.Z
@@ -274,11 +321,48 @@ The vote has passed with the following r
+1 (binding): <<list of names>>
+1 (non binding): <<list of names>>
-I will promote the artifacts to the central repo.</pre></div><p>If the vote is unsuccessful, the process will need to be restarted. Be sure to drop your staging repository as described in <a class="externalLink" href="http://www.apache.org/dev/publishing-maven-artifacts.html#drop">Dropping a Repo</a>.</p></div><div class="section"><h3>Copy the source release to the Apache Distribution Area<a name="Copy_the_source_release_to_the_Apache_Distribution_Area"></a></h3><p>The official Apache release is the 'source-release' bundle. All releases must be copied to the official release area. The release area is maintained with svnsubpub. To deliver a release, you add it to the subversion repository for the dist area.</p><p>The Maven dist area is https://dist.apache.org/repos/dist/release/maven. In here, you will find a series of subdirectories (plugins, scm, etc, etc.) Add the release, its signatures, and corresponding MD5 files. Currently this need to be in maven-pmc group. ( See <a c
lass="externalLink" href="https://issues.apache.org/jira/browse/INFRA-5945">https://issues.apache.org/jira/browse/INFRA-5945</a> ) For example:</p><div class="source"><pre>wagon/wagon-2.2-source-release.zip
+I will promote the artifacts to the central repo.</pre></div>
+<p>If the vote is unsuccessful, the process will need to be restarted. Be sure to drop your staging repository as described in <a class="externalLink" href="http://www.apache.org/dev/publishing-maven-artifacts.html#drop">Dropping a Repo</a>.</p></div>
+<div class="section">
+<h3>Copy the source release to the Apache Distribution Area<a name="Copy_the_source_release_to_the_Apache_Distribution_Area"></a></h3>
+<p>The official Apache release is the 'source-release' bundle. All releases must be copied to the official release area. The release area is maintained with svnsubpub. To deliver a release, you add it to the subversion repository for the dist area.</p>
+<p>The Maven dist area is https://dist.apache.org/repos/dist/release/maven. In here, you will find a series of subdirectories (plugins, scm, etc, etc.) Add the release, its signatures, and corresponding MD5 files. Currently this need to be in maven-pmc group. ( See <a class="externalLink" href="https://issues.apache.org/jira/browse/INFRA-5945">https://issues.apache.org/jira/browse/INFRA-5945</a> ) For example:</p>
+<div class="source">
+<pre>wagon/wagon-2.2-source-release.zip
wagon/wagon-2.2-source-release.zip.asc
-wagon/wagon-2.2-source-release.zip.md5</pre></div><p>You should also run 'svn rm' as needed to clear out older releases. As per <a class="externalLink" href="http://www.apache.org/dev/release.html#where-do-releases-go">the policy</a>, only the latest release on a branch should stay in the main dist areas. So long as the previous release is at least a day old, the automatic archiver will have copied it to the archive.</p></div><div class="section"><h3>Promote the release<a name="Promote_the_release"></a></h3><p>Once the release is deemed fit for public consumption it can be transfered to a production repository where it will be available to all users.</p><ol style="list-style-type: decimal"><li>See <a class="externalLink" href="http://www.apache.org/dev/publishing-maven-artifacts.html#promote">Promoting a Repo</a> for details on promotion.</li><li>Deploy the current website<p>As above, deploy the web site if appropriate and update the project site for the new release.</p></li
><li>Update the version tracking in JIRA<p>In the relevant project, go to Administration, then Versions. Mark the <tt>Y.Z</tt> version as 'released'. Create version <tt>Y.Z+1</tt>, if that hasn't already been done. You may also archive any deprecated releases (milestones or alphas) at this time.</p></li><li>Wait for everything to sync<ol style="list-style-type: lower-alpha"><li>Sync to Maven Central<p>The sync into central staging from repository.apache.org occurs every 4 hours. There is a separate hourly schedule that runs which pushes from staging to the other central machines, and then updates the indexes.</p></li><li>Sync to Maven Website<p>If the project you are releasing doesn't yet use svnpubsub for site deployment, the deployment of the Maven website will <a class="externalLink" href="http://www.apache.org/dev/release-publishing.html#sync-delay">take an hour or so to sync</a>.</p></li></ol></li><li>Create an announcement.<ol style="list-style-type: lower-alpha"><li>U
sing Maven Changes Plugin<p>If you are releasing a plugin or a shared component you can let Maven Changes Plugin <b>generate</b>, and eventually even <b>send</b>, the announcement for you. First make sure that you have configured the necessary properties in your <a href="../committer-settings.html">committer settings</a>.</p><div class="source"><pre>cd target/checkout
-mvn changes:announcement-mail -Papache-release</pre></div><p>If sending the mail should fail, the generated annoucement is available in <tt>target/annoucement</tt> (see <tt>annoucement.vm</tt>) and you can use it as a base for sending the mail manually.</p><p>If your SMTP server requires authentication you need to add the command line options for it:</p><div class="source"><pre>cd target/checkout
-mvn changes:announcement-mail -Dchanges.username=<SMTP-USERNAME> -Dchanges.password=<SMTP-PASSWORD> -Papache-release</pre></div></li><li>Manually<p><b>Note:</b> You must send this email from your apache email account, e.g. YOUR_APACHE_USERNAME@apache.org otherwise the email to announce@maven.apache.org will bounce.</p><div class="source"><pre>From: YOUR_APACHE_USERNAME@apache.org
+wagon/wagon-2.2-source-release.zip.md5</pre></div>
+<p>You should also run 'svn rm' as needed to clear out older releases. As per <a class="externalLink" href="http://www.apache.org/dev/release.html#where-do-releases-go">the policy</a>, only the latest release on a branch should stay in the main dist areas. So long as the previous release is at least a day old, the automatic archiver will have copied it to the archive.</p></div>
+<div class="section">
+<h3>Promote the release<a name="Promote_the_release"></a></h3>
+<p>Once the release is deemed fit for public consumption it can be transfered to a production repository where it will be available to all users.</p>
+<ol style="list-style-type: decimal">
+<li>See <a class="externalLink" href="http://www.apache.org/dev/publishing-maven-artifacts.html#promote">Promoting a Repo</a> for details on promotion.</li>
+<li>Deploy the current website
+<p>As above, deploy the web site if appropriate and update the project site for the new release.</p></li>
+<li>Update the version tracking in JIRA
+<p>In the relevant project, go to Administration, then Versions. Mark the <tt>Y.Z</tt> version as 'released'. Create version <tt>Y.Z+1</tt>, if that hasn't already been done. You may also archive any deprecated releases (milestones or alphas) at this time.</p></li>
+<li>Wait for everything to sync
+<ol style="list-style-type: lower-alpha">
+<li>Sync to Maven Central
+<p>The sync into central staging from repository.apache.org occurs every 4 hours. There is a separate hourly schedule that runs which pushes from staging to the other central machines, and then updates the indexes.</p></li>
+<li>Sync to Maven Website
+<p>If the project you are releasing doesn't yet use svnpubsub for site deployment, the deployment of the Maven website will <a class="externalLink" href="http://www.apache.org/dev/release-publishing.html#sync-delay">take an hour or so to sync</a>.</p></li></ol></li>
+<li>Create an announcement.
+<ol style="list-style-type: lower-alpha">
+<li>Using Maven Changes Plugin
+<p>If you are releasing a plugin or a shared component you can let Maven Changes Plugin <b>generate</b>, and eventually even <b>send</b>, the announcement for you. First make sure that you have configured the necessary properties in your <a href="../committer-settings.html">committer settings</a>.</p>
+<div class="source">
+<pre>cd target/checkout
+mvn changes:announcement-mail -Papache-release</pre></div>
+<p>If sending the mail should fail, the generated annoucement is available in <tt>target/annoucement</tt> (see <tt>annoucement.vm</tt>) and you can use it as a base for sending the mail manually.</p>
+<p>If your SMTP server requires authentication you need to add the command line options for it:</p>
+<div class="source">
+<pre>cd target/checkout
+mvn changes:announcement-mail -Dchanges.username=<SMTP-USERNAME> -Dchanges.password=<SMTP-PASSWORD> -Papache-release</pre></div></li>
+<li>Manually
+<p><b>Note:</b> You must send this email from your apache email account, e.g. YOUR_APACHE_USERNAME@apache.org otherwise the email to announce@maven.apache.org will bounce.</p>
+<div class="source">
+<pre>From: YOUR_APACHE_USERNAME@apache.org
To: announce@maven.apache.org, users@maven.apache.org
Cc: dev@maven.apache.org
Subject: [ANN] Maven XXX Plugin Y.Z Released
@@ -304,7 +388,12 @@ Release Notes - Maven 2.x XXX Plugin - V
Enjoy,
-The Apache Maven team
-</pre></div></li></ol></li><li>Add the release to the next board report, in the private subversion area.<p>This is a PMC activity. If you are not a PMC member then email the Developer's list with a request to update this file for your release.</p></li><li>If releasing the Apache Parent POM, notify release-discuss@apache.org<p>Several projects follow this list, and should be made aware of changes to the common parent. This might also be a step to take if other shared resources are released, or if plugin releases are of particular interest to that group.</p></li><li>Celebrate :o)</li></ol></div></div>
+</pre></div></li></ol></li>
+<li>Add the release to the next board report, in the private subversion area.
+<p>This is a PMC activity. If you are not a PMC member then email the Developer's list with a request to update this file for your release.</p></li>
+<li>If releasing the Apache Parent POM, notify release-discuss@apache.org
+<p>Several projects follow this list, and should be made aware of changes to the common parent. This might also be a step to take if other shared resources are released, or if plugin releases are of particular interest to that group.</p></li>
+<li>Celebrate :o)</li></ol></div></div>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/developers/release/maven-shared-release.html
==============================================================================
--- websites/staging/maven/trunk/content/developers/release/maven-shared-release.html (original)
+++ websites/staging/maven/trunk/content/developers/release/maven-shared-release.html Sat Apr 27 07:29:22 2013
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at Apr 23, 2013
+ | Generated by Apache Maven Doxia at Apr 27, 2013
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -15,7 +15,7 @@
<meta name="author" content="Jason van Zyl
bimargulies" />
<meta name="Date-Creation-yyyymmdd" content="20130223" />
- <meta name="Date-Revision-yyyymmdd" content="20130423" />
+ <meta name="Date-Revision-yyyymmdd" content="20130427" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -45,7 +45,7 @@ bimargulies" />
Releasing A Maven Shared Component
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -233,11 +233,37 @@ bimargulies" />
</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 Shared Component<a name="Releasing_A_Maven_Shared_Compone
nt"></a></h2><p>Releasing a Maven component 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 components 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 shared component parent POM is configured to stage the documentation in a "versioned" directory such as <tt>/shared-archives/maven-XXX-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/checkout
-mvn site site-deploy -Preporting</pre></div></li></ol><p>deployed to <a class="externalLink" href="http://maven.apache.org/shared-archives/">http://maven.apache.org/shared-archives/</a>maven-XXX-Y.Z/</p></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>Or </p><div class="source"><pre>svn rm https://svn.apache.org/repos/infra/websites/production/maven/content/shared/maven-XXX
+ <!-- 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 Shared Component<a name="Releasing_A_Maven_Shared_Component"></a></h2>
+<p>Releasing a Maven component 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 components 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 shared component parent POM is configured to stage the documentation in a "versioned" directory such as <tt>/shared-archives/maven-XXX-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/checkout
+mvn site site-deploy -Preporting</pre></div></li></ol>
+<p>deployed to <a class="externalLink" href="http://maven.apache.org/shared-archives/">http://maven.apache.org/shared-archives/</a>maven-XXX-Y.Z/</p></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>Or </p>
+<div class="source">
+<pre>svn rm https://svn.apache.org/repos/infra/websites/production/maven/content/shared/maven-XXX
svn cp https://svn.apache.org/repos/infra/websites/production/maven/content/shared-archives/maven-XXX-Y.Z \
- https://svn.apache.org/repos/infra/websites/production/maven/content/shared/maven-XXX</pre></div><p>To review the site, wait for the files to arrive at</p><div class="source"><pre>http://maven.apache.org/shared/maven-XXX/</pre></div></div></div>
+ https://svn.apache.org/repos/infra/websites/production/maven/content/shared/maven-XXX</pre></div>
+<p>To review the site, wait for the files to arrive at</p>
+<div class="source">
+<pre>http://maven.apache.org/shared/maven-XXX/</pre></div></div></div>
</div>
</div>
<div class="clear">
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 Apr 27 07:29:22 2013
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at Apr 23, 2013
+ | Generated by Apache Maven Doxia at Apr 27, 2013
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -15,7 +15,7 @@
<meta name="author" content="Hervé Boutemy
Dennis Lundberg" />
<meta name="Date-Creation-yyyymmdd" content="20121104" />
- <meta name="Date-Revision-yyyymmdd" content="20130423" />
+ <meta name="Date-Revision-yyyymmdd" content="20130427" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -45,7 +45,7 @@ Dennis Lundberg" />
Releasing A Parent POM
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -233,7 +233,17 @@ Dennis Lundberg" />
</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 Parent POM<a name="Releasing_A_Parent_POM"></a></h2><p>Releasin
g a Parent POM 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 Parent POMs have particular conventions for managing and deploying the project site.</p><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><div class="source"><pre>|-- pom.xml
+ <!-- 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 Parent POM<a name="Releasing_A_Parent_POM"></a></h2>
+<p>Releasing a Parent POM 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 Parent POMs have particular conventions for managing and deploying the project site.</p>
+<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>
+<div class="source">
+<pre>|-- pom.xml
|-- site-pom.xml
`-- src
|-- site
@@ -241,18 +251,65 @@ Dennis Lundberg" />
`-- site-docs
|-- apt
| `-- index.apt
- `-- site.xml</pre></div><p>And the <tt>index.apt</tt> page not only contains instructions about the content of the parent POM, but it maintains a history of POM releases links and diffs.</p><p>Each specific step is done to maintain <tt>site-pom.xml</tt> and <tt>index.apt</tt> in sync with the release being released.</p></div><div class="section"><h3>Stage the release<a name="Stage_the_release"></a></h3><p>Before staging the release with usual procedure, you need to update <tt>site-pom.xml</tt> and <tt>index.apt</tt> to take the future release into account:</p><ol style="list-style-type: decimal"><li>update <tt>site-pom.xml</tt> parent POM version to match the version being released,</li><li>update <tt>src/site-docs/index.apt</tt>: add a line in the history of <tt>pom.xml</tt> for the future version, referring to the future svn release tag and date. Hint: in the diff link, the value for the <tt>r2</tt> parameter is easily found by following the previous version's link
and copying revision number.</li></ol><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 staged.</p><p>The parent POMs are configured to stage the documentation in a "versioned" 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).<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>people.apache.org</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="http://www.apache.org/dev/project-site.html">the sync</a>).</p><div class="source"><pre>http://maven.apache.org/pom/XXX-Y/</pre></div></li><li>Verify/change folder permissions to 0775 and files permissions to 0664. Log on to <tt>people.apache.org</tt> and change to the directory above the staging directory. Then run these commands:<div class="source"><pre>cd /www/maven.apache.org/pom
+ `-- site.xml</pre></div>
+<p>And the <tt>index.apt</tt> page not only contains instructions about the content of the parent POM, but it maintains a history of POM releases links and diffs.</p>
+<p>Each specific step is done to maintain <tt>site-pom.xml</tt> and <tt>index.apt</tt> in sync with the release being released.</p></div>
+<div class="section">
+<h3>Stage the release<a name="Stage_the_release"></a></h3>
+<p>Before staging the release with usual procedure, you need to update <tt>site-pom.xml</tt> and <tt>index.apt</tt> to take the future release into account:</p>
+<ol style="list-style-type: decimal">
+<li>update <tt>site-pom.xml</tt> parent POM version to match the version being released,</li>
+<li>update <tt>src/site-docs/index.apt</tt>: add a line in the history of <tt>pom.xml</tt> for the future version, referring to the future svn release tag and date. Hint: in the diff link, the value for the <tt>r2</tt> parameter is easily found by following the previous version's link and copying revision number.</li></ol>
+<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 staged.</p>
+<p>The parent POMs are configured to stage the documentation in a "versioned" 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).
+<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>people.apache.org</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="http://www.apache.org/dev/project-site.html">the sync</a>).</p>
+<div class="source">
+<pre>http://maven.apache.org/pom/XXX-Y/</pre></div></li>
+<li>Verify/change folder permissions to 0775 and files permissions to 0664. Log on to <tt>people.apache.org</tt> and change to the directory above the staging directory. Then run these commands:
+<div class="source">
+<pre>cd /www/maven.apache.org/pom
find . -type d -exec chmod a+rx,g+w {} \;
-find . -type f -exec chmod 664 {} \;</pre></div></li></ol></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><div class="source"><pre>...
+find . -type f -exec chmod 664 {} \;</pre></div></li></ol></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>
+<div class="source">
+<pre>...
Hi,
Changes since the last release:
http://svn.apache.org/viewvc/maven/pom/tags/<TAG>/pom.xml?r1=HEAD&r2=<REVISION-OF-LAST-RELEASE>&diff_format=h
Staging repo:
-...</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 -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="http://www.nabble.com/forum/ViewPost.jtp?post=24018250&framed=y">http://www.nabble.com/forum/ViewPost.jtp?post=24018250&framed=y</a></p><p>To review the site, wait for the files to arrive at</p><div class="source"><pre>http://maven.apache.org/pom/XXX/</pre></div><p>The wait is necessary to allow the site to be <a class="externalLink" href="http://www.apache.org/dev/project-site.html">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>https://svn.apache.org/repos/asf/maven/site/trunk</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> page.</p><p>Commit your changes and then deploy the site.</p><div class="source"><pre>mvn clean site-deploy</pre></div></div></div>
+...</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 -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="http://www.nabble.com/forum/ViewPost.jtp?post=24018250&framed=y">http://www.nabble.com/forum/ViewPost.jtp?post=24018250&framed=y</a></p>
+<p>To review the site, wait for the files to arrive at</p>
+<div class="source">
+<pre>http://maven.apache.org/pom/XXX/</pre></div>
+<p>The wait is necessary to allow the site to be <a class="externalLink" href="http://www.apache.org/dev/project-site.html">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>https://svn.apache.org/repos/asf/maven/site/trunk</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> page.</p>
+<p>Commit your changes and then deploy the site.</p>
+<div class="source">
+<pre>mvn clean site-deploy</pre></div></div></div>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/developers/release/pmc-gpg-keys.html
==============================================================================
--- websites/staging/maven/trunk/content/developers/release/pmc-gpg-keys.html (original)
+++ websites/staging/maven/trunk/content/developers/release/pmc-gpg-keys.html Sat Apr 27 07:29:22 2013
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at Apr 23, 2013
+ | Generated by Apache Maven Doxia at Apr 27, 2013
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Vincent Siveton" />
- <meta name="Date-Revision-yyyymmdd" content="20130423" />
+ <meta name="Date-Revision-yyyymmdd" content="20130427" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Developers centre - PMC Making GPG Keys
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -231,7 +231,13 @@
</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. --><!-- NOTE: For help with the syntax of this file, see: --><!-- http://maven.apache.org/doxia/referen
ces/apt-format.html --><div class="section"><h2>Introduction<a name="Introduction"></a></h2><p>You need to add your GPG keys in <a class="externalLink" href="https://svn.apache.org/repos/asf/maven/project/KEYS">https://svn.apache.org/repos/asf/maven/project/KEYS</a> before a release. Here are some useful <a class="externalLink" href="http://www.gnupg.org/">GnuPG</a> commands to generate your Keys.</p><div class="section"><h3>gpg --gen-key<a name="gpg_--gen-key"></a></h3><div class="source"><pre>>gpg --gen-key
+ <!-- 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. --><!-- NOTE: For help with the syntax of this file, see: --><!-- http://maven.apache.org/doxia/referen
ces/apt-format.html --><div class="section">
+<h2>Introduction<a name="Introduction"></a></h2>
+<p>You need to add your GPG keys in <a class="externalLink" href="https://svn.apache.org/repos/asf/maven/project/KEYS">https://svn.apache.org/repos/asf/maven/project/KEYS</a> before a release. Here are some useful <a class="externalLink" href="http://www.gnupg.org/">GnuPG</a> commands to generate your Keys.</p>
+<div class="section">
+<h3>gpg --gen-key<a name="gpg_--gen-key"></a></h3>
+<div class="source">
+<pre>>gpg --gen-key
gpg (GnuPG) 1.4.5; Copyright (C) 2006 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
@@ -304,7 +310,11 @@ pub 1024D/07DDB702 2006-10-10
Key fingerprint = 71F6 F555 8A61 71C4 330D B868 84F4 D470 07DD B702
uid Vincent Siveton <vsiveton@apache.org>
sub 2048g/D2814A59 2006-10-10
-</pre></div></div><div class="section"><h3>gpg --list-sigs<a name="gpg_--list-sigs"></a></h3><div class="source"><pre>>gpg --list-sigs "Vincent Siveton" && gpg --armor --export "Vincent Siveton"
+</pre></div></div>
+<div class="section">
+<h3>gpg --list-sigs<a name="gpg_--list-sigs"></a></h3>
+<div class="source">
+<pre>>gpg --list-sigs "Vincent Siveton" && gpg --armor --export "Vincent Siveton"
pub 1024D/07DDB702 2006-10-10
uid Vincent Siveton <vsiveton@apache.org>
sig 3 07DDB702 2006-10-10 Vincent Siveton <vsiveton@apache.org>
@@ -340,7 +350,10 @@ eekqDpx+jNmySJr6os7rPAkjx6jDUvHPiuKdT4av
CgkQhPTUcAfdtwJL9ACgmLuDxE+oZaMhyFSmXWN0fM36Bd8AoLYrvwydB9+nNnhJ
85TjkMPTgjp9
=Hg4C
------END PGP PUBLIC KEY BLOCK-----</pre></div><p>You need to append this result to <a class="externalLink" href="https://svn.apache.org/repos/asf/maven/project/KEYS">https://svn.apache.org/repos/asf/maven/project/KEYS</a>.</p><p>You also need to upload your key to the public server: <a class="externalLink" href="http://pgp.mit.edu/">http://pgp.mit.edu/</a> by copying the same you appended in the text field and submit. You can ensure by searching your email in key search engine.</p><p>You can read more about <a class="externalLink" href="http://www.apache.org/dev/release-signing.html#faq">Checksums And Signatures</a> and <a class="externalLink" href="https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven"> How to Generate PGP Signatures With Maven</a></p></div></div>
+-----END PGP PUBLIC KEY BLOCK-----</pre></div>
+<p>You need to append this result to <a class="externalLink" href="https://svn.apache.org/repos/asf/maven/project/KEYS">https://svn.apache.org/repos/asf/maven/project/KEYS</a>.</p>
+<p>You also need to upload your key to the public server: <a class="externalLink" href="http://pgp.mit.edu/">http://pgp.mit.edu/</a> by copying the same you appended in the text field and submit. You can ensure by searching your email in key search engine.</p>
+<p>You can read more about <a class="externalLink" href="http://www.apache.org/dev/release-signing.html#faq">Checksums And Signatures</a> and <a class="externalLink" href="https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven"> How to Generate PGP Signatures With Maven</a></p></div></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 Apr 27 07:29:22 2013
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at Apr 23, 2013
+ | Generated by Apache Maven Doxia at Apr 27, 2013
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -14,7 +14,7 @@
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Jason van Zyl" />
<meta name="Date-Creation-yyyymmdd" content="20100726" />
- <meta name="Date-Revision-yyyymmdd" content="20130423" />
+ <meta name="Date-Revision-yyyymmdd" content="20130427" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -44,7 +44,7 @@
Releasing A Maven Project
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -232,7 +232,18 @@
</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 Project<a name="Releasing_A_Maven_Project"></a></h2><p>Wh
at 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><ul><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><ul><li><a href="./maven-project-release-procedure.html"> Maven Project Common Release procedure</a></li></ul></div>
+ <!-- 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 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>
+<ul>
+<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>
+<ul>
+<li><a href="./maven-project-release-procedure.html"> Maven Project Common Release procedure</a></li></ul></div>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/developers/retirement-plan-plugins.html
==============================================================================
--- websites/staging/maven/trunk/content/developers/retirement-plan-plugins.html (original)
+++ websites/staging/maven/trunk/content/developers/retirement-plan-plugins.html Sat Apr 27 07:29:22 2013
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at Apr 23, 2013
+ | Generated by Apache Maven Doxia at Apr 27, 2013
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -14,7 +14,7 @@
<link rel="stylesheet" href="../css/print.css" type="text/css" media="print" />
<meta name="author" content="Dennis Lundberg" />
<meta name="Date-Creation-yyyymmdd" content="20101230" />
- <meta name="Date-Revision-yyyymmdd" content="20130423" />
+ <meta name="Date-Revision-yyyymmdd" content="20130427" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -44,7 +44,7 @@
Retirement Plan for Plugins
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -232,7 +232,16 @@
</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. --><!-- NOTE: For help with the syntax of this file, see: --><!-- http://maven.apache.org/doxia/referen
ces/apt-format.html --><div class="section"><h2>Retirement Plan for Plugins<a name="Retirement_Plan_for_Plugins"></a></h2><ol style="list-style-type: decimal"><li>Propose a vote on the dev-list to retire a plugin. The vote should be open for the standard 72 hours to allow people to voice their opinions. Send a cc to the users-list. Standard Apache voting rules apply. Only PMC votes are binding.<p>The vote must contain one or more options on how to retire the plugin. There are multiple scenarios available. Here are a couple that have been suggested:</p><ul><li>Move to retired area in svn</li><li>Move to mojo.codehaus.org, apache-extras.org or another forge</li></ul></li><li>Make one final release of the plugin before it is retired. This allows us to make a clean break. The final release must remove the "Source Repository" report from the site, since the SCM URLs will be changed when the plugin is retired. A prominent notice must be placed on the front page of the pl
ugin's site, informing that the plugin is retired. If the plugin is moved elsewhere, that should also be posted on the plugin's site. The person who wants to retire a plugin is the one who does the final release.</li><li>Announce the fact that the plugin has been retired/moved on the announce@m.a.o and users@m.a.o mailing lists. Explain to people what they should do if they would like to help with the continued development of the plugin.</li></ol></div>
+ <!-- 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. --><!-- NOTE: For help with the syntax of this file, see: --><!-- http://maven.apache.org/doxia/referen
ces/apt-format.html --><div class="section">
+<h2>Retirement Plan for Plugins<a name="Retirement_Plan_for_Plugins"></a></h2>
+<ol style="list-style-type: decimal">
+<li>Propose a vote on the dev-list to retire a plugin. The vote should be open for the standard 72 hours to allow people to voice their opinions. Send a cc to the users-list. Standard Apache voting rules apply. Only PMC votes are binding.
+<p>The vote must contain one or more options on how to retire the plugin. There are multiple scenarios available. Here are a couple that have been suggested:</p>
+<ul>
+<li>Move to retired area in svn</li>
+<li>Move to mojo.codehaus.org, apache-extras.org or another forge</li></ul></li>
+<li>Make one final release of the plugin before it is retired. This allows us to make a clean break. The final release must remove the "Source Repository" report from the site, since the SCM URLs will be changed when the plugin is retired. A prominent notice must be placed on the front page of the plugin's site, informing that the plugin is retired. If the plugin is moved elsewhere, that should also be posted on the plugin's site. The person who wants to retire a plugin is the one who does the final release.</li>
+<li>Announce the fact that the plugin has been retired/moved on the announce@m.a.o and users@m.a.o mailing lists. Explain to people what they should do if they would like to help with the continued development of the plugin.</li></ol></div>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/developers/website/deploy-maven-current-ref.html
==============================================================================
--- websites/staging/maven/trunk/content/developers/website/deploy-maven-current-ref.html (original)
+++ websites/staging/maven/trunk/content/developers/website/deploy-maven-current-ref.html Sat Apr 27 07:29:22 2013
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at Apr 23, 2013
+ | Generated by Apache Maven Doxia at Apr 27, 2013
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Vincent Siveton" />
- <meta name="Date-Revision-yyyymmdd" content="20130423" />
+ <meta name="Date-Revision-yyyymmdd" content="20130427" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Deploy Maven Current References
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -231,7 +231,36 @@
</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. --><!-- NOTE: For help with the syntax of this file, see: --><!-- http://maven.apache.org/doxia/referen
ces/apt-format.html --><div class="section"><h2>Introduction<a name="Introduction"></a></h2><p>This document gives step-by-step instructions for deploying the <a href="/ref/current/">Maven current references</a>. The primary audience is Maven PMC.</p></div><div class="section"><h2>Prerequisite<a name="Prerequisite"></a></h2><p>Be sure that:</p><ul><li>you have all Maven servers defined in your <tt>settings.xml</tt>. For more information, please refer to <a href="../committer-settings.html">Committer settings</a>.</li><li>you have created your GPG keys. For more information, please refer to <a href="../release/pmc-gpg-keys.html">Making GPG Keys</a>.</li></ul></div><div class="section"><h2>Deploy Maven Current References<a name="Deploy_Maven_Current_References"></a></h2><ol style="list-style-type: decimal"><li>Do a fresh check out of a release tag of Maven, for example:<div class="source"><pre>$ svn checkout https://svn.apache.org/repos/asf/maven/maven-2/tags/maven-2.2.0 maven
-2.2.0</pre></div></li><li>Execute the site goal for the <i>maven-2.2.0</i> project<div class="source"><pre>maven-2.2.0$ mvn site -Preporting</pre></div></li><li>Verify the documentation before deploying<p>You could also use the <i>stage</i> goal of the Maven Site Plugin to verify the site output. For instance:</p><div class="source"><pre>maven-2.2.0$ mvn site:stage -Preporting -DstagingDirectory=/tmp/maven-2.2.0</pre></div></li><li>Deploy to people.apache.org<div class="source"><pre>maven-2.2.0$ mvn site-deploy -Preporting</pre></div><p>It will create a new folder <i>2.2.0</i> in <i><a href="/ref/">/www/maven.apache.org/ref/</a></i> on the Apache server.</p><p><b>Note:</b> It will <a class="externalLink" href="http://www.apache.org/dev/release-publishing.html#sync-delay">take an hour or so to sync</a>.</p></li></ol></div><div class="section"><h2>Information on <tt><a href="/ref/current">/ref/current</a></tt> mechanism<a name="Information_on_refcurrent_mechanism"></a></h2><p
>The redirection from <tt><a href="/ref/current">/ref/current</a></tt> to actual Maven version reference is done through <tt><a class="externalLink" href="http://svn.apache.org/viewvc/maven/site/trunk/src/site/filtered-resources/.htaccess?view=markup">.htaccess</a></tt> published in site. </p></div>
+ <!-- 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. --><!-- NOTE: For help with the syntax of this file, see: --><!-- http://maven.apache.org/doxia/referen
ces/apt-format.html --><div class="section">
+<h2>Introduction<a name="Introduction"></a></h2>
+<p>This document gives step-by-step instructions for deploying the <a href="/ref/current/">Maven current references</a>. The primary audience is Maven PMC.</p></div>
+<div class="section">
+<h2>Prerequisite<a name="Prerequisite"></a></h2>
+<p>Be sure that:</p>
+<ul>
+<li>you have all Maven servers defined in your <tt>settings.xml</tt>. For more information, please refer to <a href="../committer-settings.html">Committer settings</a>.</li>
+<li>you have created your GPG keys. For more information, please refer to <a href="../release/pmc-gpg-keys.html">Making GPG Keys</a>.</li></ul></div>
+<div class="section">
+<h2>Deploy Maven Current References<a name="Deploy_Maven_Current_References"></a></h2>
+<ol style="list-style-type: decimal">
+<li>Do a fresh check out of a release tag of Maven, for example:
+<div class="source">
+<pre>$ svn checkout https://svn.apache.org/repos/asf/maven/maven-2/tags/maven-2.2.0 maven-2.2.0</pre></div></li>
+<li>Execute the site goal for the <i>maven-2.2.0</i> project
+<div class="source">
+<pre>maven-2.2.0$ mvn site -Preporting</pre></div></li>
+<li>Verify the documentation before deploying
+<p>You could also use the <i>stage</i> goal of the Maven Site Plugin to verify the site output. For instance:</p>
+<div class="source">
+<pre>maven-2.2.0$ mvn site:stage -Preporting -DstagingDirectory=/tmp/maven-2.2.0</pre></div></li>
+<li>Deploy to people.apache.org
+<div class="source">
+<pre>maven-2.2.0$ mvn site-deploy -Preporting</pre></div>
+<p>It will create a new folder <i>2.2.0</i> in <i><a href="/ref/">/www/maven.apache.org/ref/</a></i> on the Apache server.</p>
+<p><b>Note:</b> It will <a class="externalLink" href="http://www.apache.org/dev/release-publishing.html#sync-delay">take an hour or so to sync</a>.</p></li></ol></div>
+<div class="section">
+<h2>Information on <tt><a href="/ref/current">/ref/current</a></tt> mechanism<a name="Information_on_refcurrent_mechanism"></a></h2>
+<p>The redirection from <tt><a href="/ref/current">/ref/current</a></tt> to actual Maven version reference is done through <tt><a class="externalLink" href="http://svn.apache.org/viewvc/maven/site/trunk/src/site/filtered-resources/.htaccess?view=markup">.htaccess</a></tt> published in site. </p></div>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/developers/website/deploy-maven-website.html
==============================================================================
--- websites/staging/maven/trunk/content/developers/website/deploy-maven-website.html (original)
+++ websites/staging/maven/trunk/content/developers/website/deploy-maven-website.html Sat Apr 27 07:29:22 2013
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at Apr 23, 2013
+ | Generated by Apache Maven Doxia at Apr 27, 2013
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -14,7 +14,7 @@
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Barrie Treloar" />
<meta name="Date-Creation-yyyymmdd" content="20121211" />
- <meta name="Date-Revision-yyyymmdd" content="20130423" />
+ <meta name="Date-Revision-yyyymmdd" content="20130427" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -44,7 +44,7 @@
Deploy Maven Website
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -232,7 +232,46 @@
</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. --><!-- NOTE: For help with the syntax of this file, see: --><!-- http://maven.apache.org/doxia/referen
ces/apt-format.html --><div class="section"><h2>Introduction<a name="Introduction"></a></h2><p>This document gives step-by-step instructions for deploying the Maven website <a class="externalLink" href="http://maven.apache.org">http://maven.apache.org</a>.</p><p>Since 10th December 2012, the main website use CMS mechanism. (see <a class="externalLink" href="https://cms.apache.org/maven/">https://cms.apache.org/maven/</a>).</p><p>You can edit pages in two ways:</p><ul><li>use the CMS UI.</li><li>checkout the content locally and modify manually.</li></ul></div><div class="section"><h2>How it works<a name="How_it_works"></a></h2><p>At least how a user understand that.</p><p>All the content is located here https://svn.apache.org/repos/infra/websites/production/maven/content/ then synced to lives machines.</p><p>For parts edited/build with CMS, two buildbot jobs build the content via using Maven site plugin:</p><ul><li><a class="externalLink" href="http://ci.apache.org/builders/m
aven-site-staging">http://ci.apache.org/builders/maven-site-staging</a></li><li><a class="externalLink" href="http://ci.apache.org/builders/maven-doxia-site-staging">http://ci.apache.org/builders/maven-doxia-site-staging</a></li></ul><p>Other parts can committed to the content source tree.</p><p>As CMS will delete non build content, they must be ignored with adding paths in extpaths.txt file (located in site and doxia-site in path content/resources)</p><div class="section"><h3>Modify Maven Website with CMS UI<a name="Modify_Maven_Website_with_CMS_UI"></a></h3><ul><li>Go to <a class="externalLink" href="https://cms.apache.org/maven/">https://cms.apache.org/maven/</a>.</li><li>Click link "Get maven Working Copy".</li><li>Now navigate to the content you want to modify.</li><li>Once you have modified the content, you can now commit with the button "Submit".</li></ul></div><div class="section"><h3>Modify Maven Website with a local copy<a name="Modify_Maven_Web
site_with_a_local_copy"></a></h3><ol style="list-style-type: decimal"><li>Do a fresh check out of the Maven site, for example:<div class="source"><pre>$ svn checkout https://svn.apache.org/repos/asf/maven/site site</pre></div></li><li>Execute the site goal<div class="source"><pre>mvn site </pre></div></li><li>Verify the documentation before committing</li></ol></div></div><div class="section"><h2>Publish content<a name="Publish_content"></a></h2><ul><li>Verify that the staging content has been build with buildbot job (<a class="externalLink" href="http://ci.apache.org/builders/maven-site-staging">http://ci.apache.org/builders/maven-site-staging</a>) to <a class="externalLink" href="http://maven.staging.apache.org">http://maven.staging.apache.org</a> </li><li>If everything is good, publish modifications using <a class="externalLink" href="https://cms.apache.org/maven/publish">https://cms.apache.org/maven/publish</a></li></ul></div>
+ <!-- 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. --><!-- NOTE: For help with the syntax of this file, see: --><!-- http://maven.apache.org/doxia/referen
ces/apt-format.html --><div class="section">
+<h2>Introduction<a name="Introduction"></a></h2>
+<p>This document gives step-by-step instructions for deploying the Maven website <a class="externalLink" href="http://maven.apache.org">http://maven.apache.org</a>.</p>
+<p>Since 10th December 2012, the main website use CMS mechanism. (see <a class="externalLink" href="https://cms.apache.org/maven/">https://cms.apache.org/maven/</a>).</p>
+<p>You can edit pages in two ways:</p>
+<ul>
+<li>use the CMS UI.</li>
+<li>checkout the content locally and modify manually.</li></ul></div>
+<div class="section">
+<h2>How it works<a name="How_it_works"></a></h2>
+<p>At least how a user understand that.</p>
+<p>All the content is located here https://svn.apache.org/repos/infra/websites/production/maven/content/ then synced to lives machines.</p>
+<p>For parts edited/build with CMS, two buildbot jobs build the content via using Maven site plugin:</p>
+<ul>
+<li><a class="externalLink" href="http://ci.apache.org/builders/maven-site-staging">http://ci.apache.org/builders/maven-site-staging</a></li>
+<li><a class="externalLink" href="http://ci.apache.org/builders/maven-doxia-site-staging">http://ci.apache.org/builders/maven-doxia-site-staging</a></li></ul>
+<p>Other parts can committed to the content source tree.</p>
+<p>As CMS will delete non build content, they must be ignored with adding paths in extpaths.txt file (located in site and doxia-site in path content/resources)</p>
+<div class="section">
+<h3>Modify Maven Website with CMS UI<a name="Modify_Maven_Website_with_CMS_UI"></a></h3>
+<ul>
+<li>Go to <a class="externalLink" href="https://cms.apache.org/maven/">https://cms.apache.org/maven/</a>.</li>
+<li>Click link "Get maven Working Copy".</li>
+<li>Now navigate to the content you want to modify.</li>
+<li>Once you have modified the content, you can now commit with the button "Submit".</li></ul></div>
+<div class="section">
+<h3>Modify Maven Website with a local copy<a name="Modify_Maven_Website_with_a_local_copy"></a></h3>
+<ol style="list-style-type: decimal">
+<li>Do a fresh check out of the Maven site, for example:
+<div class="source">
+<pre>$ svn checkout https://svn.apache.org/repos/asf/maven/site site</pre></div></li>
+<li>Execute the site goal
+<div class="source">
+<pre>mvn site </pre></div></li>
+<li>Verify the documentation before committing</li></ol></div></div>
+<div class="section">
+<h2>Publish content<a name="Publish_content"></a></h2>
+<ul>
+<li>Verify that the staging content has been build with buildbot job (<a class="externalLink" href="http://ci.apache.org/builders/maven-site-staging">http://ci.apache.org/builders/maven-site-staging</a>) to <a class="externalLink" href="http://maven.staging.apache.org">http://maven.staging.apache.org</a> </li>
+<li>If everything is good, publish modifications using <a class="externalLink" href="https://cms.apache.org/maven/publish">https://cms.apache.org/maven/publish</a></li></ul></div>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/developers/welcome-to-new-committers.html
==============================================================================
--- websites/staging/maven/trunk/content/developers/welcome-to-new-committers.html (original)
+++ websites/staging/maven/trunk/content/developers/welcome-to-new-committers.html Sat Apr 27 07:29:22 2013
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at Apr 23, 2013
+ | Generated by Apache Maven Doxia at Apr 27, 2013
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../css/print.css" type="text/css" media="print" />
<meta name="author" content="The Maven Team" />
- <meta name="Date-Revision-yyyymmdd" content="20130423" />
+ <meta name="Date-Revision-yyyymmdd" content="20130427" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Guide for new Maven committers
</div>
<div class="xright">
- Last Published: 2013-04-23
+ Last Published: 2013-04-27
</div>
<div class="clear">
<hr/>
@@ -231,7 +231,25 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2>Guide for new Maven committers<a name="Guide_for_new_Maven_committers"></a></h2><p>First of all congratulations, thank you, and welcome to the fold! If you are reading this you've recently been voted in as committer on an Apache Maven project and there are a few things that need to be sorted out before you can participate fully.</p><p>The first thing to get out of the way is sending in your contributor's license agreement (CLA). You can't participate at Apache until we have received your signed CLA, so go to the <a class="externalLink" href="http://www.apache.org/licenses/#clas">Apache website</a>, print out the CLA, sign it, and send it in ASAP.</p><p>Once you've dealt with your CLA, there are a some documents that pertain to Apache as a whole you should read:</p><ul><li><a class="externalLink" href="http://www.apache.org/foundation/how-it-works.html">How the ASF works</a></li><li><a class="externalLink" href="http://www.apache.org/dev/new-c
ommitters-guide.html">Guide for new committers</a></li><li><a class="externalLink" href="http://www.apache.org/dev/committers.html">The committers FAQ</a></li><li><a class="externalLink" href="http://www.apache.org/foundation/voting.html">How voting works</a> </li></ul><p>Here are the documents that pertain to Maven specifically:</p><ul><li><a class="externalLink" href="http://maven.apache.org/guides/development/guide-m2-development.html">Guide to Maven 2 development</a></li></ul></div><div class="section"><h2>And here are the specifics on setting up your SVN access:<a name="And_here_are_the_specifics_on_setting_up_your_SVN_access:"></a></h2><div class="section"><h3><a class="externalLink" href="http://www.apache.org/dev/version-control.html">Apache's Source Code Repository</a><a name="Apaches_Source_Code_Repository"></a></h3><p>If you have any questions just ask! We're here to help, and looking forward to working with you!</p><p>The Maven Team!</p></div></div>
+ <div class="section">
+<h2>Guide for new Maven committers<a name="Guide_for_new_Maven_committers"></a></h2>
+<p>First of all congratulations, thank you, and welcome to the fold! If you are reading this you've recently been voted in as committer on an Apache Maven project and there are a few things that need to be sorted out before you can participate fully.</p>
+<p>The first thing to get out of the way is sending in your contributor's license agreement (CLA). You can't participate at Apache until we have received your signed CLA, so go to the <a class="externalLink" href="http://www.apache.org/licenses/#clas">Apache website</a>, print out the CLA, sign it, and send it in ASAP.</p>
+<p>Once you've dealt with your CLA, there are a some documents that pertain to Apache as a whole you should read:</p>
+<ul>
+<li><a class="externalLink" href="http://www.apache.org/foundation/how-it-works.html">How the ASF works</a></li>
+<li><a class="externalLink" href="http://www.apache.org/dev/new-committers-guide.html">Guide for new committers</a></li>
+<li><a class="externalLink" href="http://www.apache.org/dev/committers.html">The committers FAQ</a></li>
+<li><a class="externalLink" href="http://www.apache.org/foundation/voting.html">How voting works</a> </li></ul>
+<p>Here are the documents that pertain to Maven specifically:</p>
+<ul>
+<li><a class="externalLink" href="http://maven.apache.org/guides/development/guide-m2-development.html">Guide to Maven 2 development</a></li></ul></div>
+<div class="section">
+<h2>And here are the specifics on setting up your SVN access:<a name="And_here_are_the_specifics_on_setting_up_your_SVN_access:"></a></h2>
+<div class="section">
+<h3><a class="externalLink" href="http://www.apache.org/dev/version-control.html">Apache's Source Code Repository</a><a name="Apaches_Source_Code_Repository"></a></h3>
+<p>If you have any questions just ask! We're here to help, and looking forward to working with you!</p>
+<p>The Maven Team!</p></div></div>
</div>
</div>
<div class="clear">