You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by iv...@apache.org on 2011/01/13 08:35:31 UTC
svn commit: r1058436 - in /wicket/common/site/trunk: _site/atom.xml
_site/contribute/release.html contribute/release.md
Author: ivaynberg
Date: Thu Jan 13 07:35:31 2011
New Revision: 1058436
URL: http://svn.apache.org/viewvc?rev=1058436&view=rev
Log:
release page tweaks. merged Michael's patch from WICKET-3294
Modified:
wicket/common/site/trunk/_site/atom.xml
wicket/common/site/trunk/_site/contribute/release.html
wicket/common/site/trunk/contribute/release.md
Modified: wicket/common/site/trunk/_site/atom.xml
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/atom.xml?rev=1058436&r1=1058435&r2=1058436&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/atom.xml (original)
+++ wicket/common/site/trunk/_site/atom.xml Thu Jan 13 07:35:31 2011
@@ -4,7 +4,7 @@
<title>Apache Wicket</title>
<link href="http://wicket.apache.org/atom.xml" rel="self"/>
<link href="http://wicket.apache.org/"/>
- <updated>2011-01-11T20:42:35-06:00</updated>
+ <updated>2011-01-12T23:33:51-08:00</updated>
<id>http://wicket.apache.org/</id>
<author>
<name>Apache Wicket</name>
@@ -15,7 +15,7 @@
<entry>
<title>Wicket 1.4.15 released</title>
<link href="http://wicket.apache.org/2010/12/24/wicket-1.4.15-released.html"/>
- <updated>2010-12-24T00:00:00-06:00</updated>
+ <updated>2010-12-24T00:00:00-08:00</updated>
<id>http://wicket.apache.org/2010/12/24/wicket-1.4.15-released</id>
<content type="html"><p>This is fifteenth release of the Wicket 1.4.x series. This is primarily a minor bugfix release on the 1.4.x (stable) branch.</p>
@@ -41,7 +41,7 @@
<entry>
<title>Wicket 1.4.14 released</title>
<link href="http://wicket.apache.org/2010/11/29/wicket-1.4.14-released.html"/>
- <updated>2010-11-29T00:00:00-06:00</updated>
+ <updated>2010-11-29T00:00:00-08:00</updated>
<id>http://wicket.apache.org/2010/11/29/wicket-1.4.14-released</id>
<content type="html"><p>This is fourteenth release of the Wicket 1.4.x series. This is primarily a minor bugfix release on the 1.4.x (stable) branch.</p>
@@ -67,7 +67,7 @@
<entry>
<title>Pedro Santos is a Wicket team member</title>
<link href="http://wicket.apache.org/2010/11/21/pedro-santos-committer.html"/>
- <updated>2010-11-21T00:00:00-06:00</updated>
+ <updated>2010-11-21T00:00:00-08:00</updated>
<id>http://wicket.apache.org/2010/11/21/pedro-santos-committer</id>
<content type="html"><p>Pedro Santos has been added as a committer and PMC member for Apache Wicket. Pedro has been increasingly active in the Wicket community in recent months, and his patches continue to improve in quality. Additionally, Pedro is always willing to do the &#8220;grunt work&#8221; of creating great test cases for his patches, or for JIRA issues that others have attached patches to. Test cases are invaluable to the development of Wicket because they help us not introduce regressions as we fix bugs and add features.</p>
@@ -77,7 +77,7 @@
<entry>
<title>Wicket 1.5-M3 released</title>
<link href="http://wicket.apache.org/2010/11/05/wicket-1.5-M3-released.html"/>
- <updated>2010-11-05T00:00:00-05:00</updated>
+ <updated>2010-11-05T00:00:00-07:00</updated>
<id>http://wicket.apache.org/2010/11/05/wicket-1.5-M3-released</id>
<content type="html"><p>This is another milestone release from trunk (in-development branch). This release includes several enhancments and fixes, which can be seen in the changelog (linked below).</p>
@@ -103,7 +103,7 @@
<entry>
<title>Wicket 1.4.13 released</title>
<link href="http://wicket.apache.org/2010/11/01/wicket-1.4.13-released.html"/>
- <updated>2010-11-01T00:00:00-05:00</updated>
+ <updated>2010-11-01T00:00:00-07:00</updated>
<id>http://wicket.apache.org/2010/11/01/wicket-1.4.13-released</id>
<content type="html"><p>This is thirteenth release of the Wicket 1.4.x series. This is primarily a minor bugfix release on the 1.4.x (stable) branch.</p>
@@ -129,7 +129,7 @@
<entry>
<title>Wicket 1.5-M2.1 released</title>
<link href="http://wicket.apache.org/2010/09/17/wicket.1.5-M2.1-released.html"/>
- <updated>2010-09-17T00:00:00-05:00</updated>
+ <updated>2010-09-17T00:00:00-07:00</updated>
<id>http://wicket.apache.org/2010/09/17/wicket.1.5-M2.1-released</id>
<content type="html"><p>This is the second milestone of the new 1.5.x Wicket series. The focus of 1.5.x is to provide our users with a more powerful and flexible request processing pipeline.</p>
@@ -159,7 +159,7 @@
<entry>
<title>Wicket 1.4.12 released</title>
<link href="http://wicket.apache.org/2010/09/17/wicket.1.4.12-released.html"/>
- <updated>2010-09-17T00:00:00-05:00</updated>
+ <updated>2010-09-17T00:00:00-07:00</updated>
<id>http://wicket.apache.org/2010/09/17/wicket.1.4.12-released</id>
<content type="html"><p>This is the twelfth maintenance release of the 1.4.x series. This release brings a fix to a <a href='https://issues.apache.org/jira/browse/WICKET-3040'>critical bug</a> which prevented ajax form submits in FireFox.</p>
@@ -185,7 +185,7 @@
<entry>
<title>Wicket 1.4.11 released</title>
<link href="http://wicket.apache.org/2010/09/09/wicket-1.4.11-released.html"/>
- <updated>2010-09-09T00:00:00-05:00</updated>
+ <updated>2010-09-09T00:00:00-07:00</updated>
<id>http://wicket.apache.org/2010/09/09/wicket-1.4.11-released</id>
<content type="html"><p>This is the eleventh maintenance release of the 1.4.x series and brings over fifty bug fixes and improvements.</p>
@@ -211,7 +211,7 @@
<entry>
<title>Peter Ertl is a Wicket team member</title>
<link href="http://wicket.apache.org/2010/08/24/peter-ertl-committer.html"/>
- <updated>2010-08-24T00:00:00-05:00</updated>
+ <updated>2010-08-24T00:00:00-07:00</updated>
<id>http://wicket.apache.org/2010/08/24/peter-ertl-committer</id>
<content type="html"><p>The Apache Wicket team is proud to have Peter Ertl as a new member to the team of developers. Peter has been active in our community for a long time now and has contributed many patches, reported many bugs as well as helping out on the user list.</p>
@@ -221,7 +221,7 @@
<entry>
<title>Wicket 1.5-M1 released</title>
<link href="http://wicket.apache.org/2010/08/11/wicket-1.5-M1-released.html"/>
- <updated>2010-08-11T00:00:00-05:00</updated>
+ <updated>2010-08-11T00:00:00-07:00</updated>
<id>http://wicket.apache.org/2010/08/11/wicket-1.5-M1-released</id>
<content type="html"><p>This is the first milestone of the new 1.5.x Wicket series. The focus of 1.5.x is to provide our users with a more powerful and flexible request processing pipeline.</p>
Modified: wicket/common/site/trunk/_site/contribute/release.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/contribute/release.html?rev=1058436&r1=1058435&r2=1058436&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/contribute/release.html (original)
+++ wicket/common/site/trunk/_site/contribute/release.html Thu Jan 13 07:35:31 2011
@@ -151,9 +151,7 @@
<li><a href='#release-13'>Releasing Apache Wicket 1.3.x</a></li>
-<li><a href='#mirrors'>Uploading to the mirror system</a></li>
-
-<li><a href='#mavencentral'>Uploading to maven repository</a></li>
+<li><a href='#nexus'>Staging Releases using the Apache Nexus Repository</a></li>
<li><a href='#announcing'>Announcing the release</a></li>
@@ -162,14 +160,35 @@
<h2 id='release-14'>Releasing Apache Wicket 1.4.x</h2>
-<h3 id='building_the_release'>Building the release</h3>
+<h3 id='building_the_release'>Building the Release</h3>
+
+<h4 id='preparing'>Preparing</h4>
<ul>
<li>Ask the dev@ mailing list if there are any issues that still need to be in the release (looking at JIRA is a good start)</li>
-<li>Assuming there are none, and you are now in build mode, update the CHANGELOG-1.4 file * you can use JIRA for this list: go to “releases”, and under “unreleased”, next to your version, there’s a release notes link</li>
+<li>Release the version in JIRA</li>
-<li>create a release branch to do your release work in (modifying poms, etc) * then checkout that release branch and cd into it</li>
+<li>Assuming there are none, and you are now in build mode, update the CHANGELOG-1.4 file (you can use JIRA for this list: go to “releases”, and under “unreleased”, next to your version, there’s a release notes link)</li>
+</ul>
+
+<p>Make sure your <code>~/.m2/settings.xml</code> contains the following definition</p>
+<div class='highlight'><pre><code class='console'><span class='go'><?xml version="1.0"?></span>
+<span class='go'><settings></span>
+<span class='go'><servers></span>
+<span class='go'> <server></span>
+<span class='go'> <id>apache.releases.https</id></span>
+<span class='go'> <username>$your_apache_username</username></span>
+<span class='go'> <password>$your_apache_password</password></span>
+<span class='go'> </server></span>
+<span class='go'></servers></span>
+<span class='go'></settings></span>
+</code></pre>
+</div>
+<ul>
+<li>create a release branch to do your release work in (modifying poms, etc)</li>
+
+<li>then checkout that release branch and cd into it</li>
</ul>
<div class='highlight'><pre><code class='console'><span class='gp'>$</span> svn cp https://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.x <span class='se'>\</span>
<span class='go'>https://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.13 \</span>
@@ -183,32 +202,42 @@
</code></pre>
</div>
<ul>
-<li>Set correct version in the pom files * Linux</li>
+<li>Set correct version in the pom files using the <a href='http://mojo.codehaus.org/versions-maven-plugin'>maven-versions-plugin</a>:</li>
</ul>
-<div class='highlight'><pre><code class='console'><span class='go'>find . -name "pom.xml" | xargs sed -i -e "s/1.4-SNAPSHOT/1.4.13/g"</span>
-<span class='go'>find . -name "pom.xml" | xargs sed -i -e "s/wicket\/trunk/wicket\/releases\/wicket-1.4.13/g"</span>
-</code></pre>
-</div>
-<pre><code>* Mac OS X</code></pre>
-<div class='highlight'><pre><code class='console'><span class='go'>find . -name "pom.xml" | xargs sed -i "" -e "s/1.4-SNAPSHOT/1.4.13/g"</span>
-<span class='go'>find . -name "pom.xml" | xargs sed -i "" -e "s/wicket\/trunk/wicket\/releases\/wicket-1.4.13/g"</span>
+<div class='highlight'><pre><code class='console'><span class='go'>mvn versions:set -DnewVersion=1.4.13</span>
+<span class='go'>... list of all changed artifacts changed.</span>
+<span class='go'>mvn versions:commit </span>
+<span class='go'>removes all of the pom.xml.versionsBackup files.</span>
</code></pre>
</div>
<ul>
-<li>Commit these modified pom files to the release branch</li>
+<li>Call release.sh (still from the checkout out release branch code) <strong>NOTE</strong> If you get an error while generating javadocs like ”<code>java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl</code>”, run a <code>mvn clean install -Dmaven.test.skip=true</code> followed by a <code>mvn javadoc:jar</code>, then re-run <code>release.sh</code>.</li>
-<li>Call release.sh (still from the checkout out release branch code) * NOTE: If you get an error while generating javadocs like ”<code>java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl</code>”, run a <code>mvn clean install -Dmaven.test.skip=true</code> followed by a <code>mvn javadoc:jar</code>, then re-run <code>release.sh</code>.</li>
+<li>Login to the Apache Nexus Repository on http://repository.apache.org; See <a href='#nexus'>Releasing with Apache Nexus</a> below.</li>
-<li>Test the distribution (examples, rat, etc)</li>
+<li>Select <strong>Staging Repositories</strong> from the left hand side, then select the repository and click <strong>Close</strong>.</li>
-<li>Upload artifacts (including signing keys) to your people.apache.org account:</li>
+<li>Test that the distribution (examples, rat, etc) is accessible from the staging repository url.</li>
+
+<li>upload non-maven artifacts to pao:</li>
</ul>
-<div class='highlight'><pre><code class='console'><span class='go'>svn export http://svn.apache.org/repos/asf/wicket/common/KEYS target/dist/KEYS</span>
-<span class='go'>ssh people.apache.org mkdir public_html/wicket-1.4.13</span>
-<span class='go'>scp -r target/dist target/m2-repo people.apache.org:public_html/wicket-1.4.13</span>
+<div class='highlight'><pre><code class='console'><span class='go'>export wicketversion=<version></span>
+<span class='go'>svn export http://svn.apache.org/repos/asf/wicket/common/KEYS target/dist/KEYS</span>
+<span class='go'>ssh people.apache.org mkdir public_html/wicket-$wicketversion</span>
+<span class='go'>scp -r target/dist target/m2-repo people.apache.org:public_html/wicket-$wicketversion</span>
</code></pre>
</div>
<ul>
+<li>Commit these modified pom files to the release branch.</li>
+
+<li>Send vote message to dev@ mailing list. Include link to the closed repository for testing against.</li>
+
+<li>Wait requisite 72 hours for the vote to pass (we hope)</li>
+
+<li>Login to repository.apache.org, select the closed repository and click <strong>Release</strong>. It will be accessible immediately through the apache release repo and then within 1-2 hours through maven central.</li>
+
+<li>If the release is voted down you can <strong>Drop</strong> the staged release and then restage later after incorporating the necessary changes.</li>
+
<li>Tag the release in SVN:</li>
</ul>
<div class='highlight'><pre><code class='console'><span class='gp'>$</span> svn cp https://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.13 <span class='se'>\</span>
@@ -218,93 +247,57 @@
</code></pre>
</div>
<ul>
-<li>Send vote message to dev@ mailing list</li>
-
-<li>Wait requisite 72 hours for the vote to pass (we hope)</li>
-
-<li>Upload to mirrors (see below)</li>
-
-<li>Release the version in JIRA</li>
+<li>Wait until repo1.maven.org has picked up the release artifacts.</li>
-<li>Wait 24 hours for mirrors to pick them up</li>
+<li>Wait 24 hours until mirrors picked up release artifacts</li>
-<li>Announce (see below)</li>
+<li>Announce (see <a href='#announcing'>below</a>)</li>
</ul>
-<a name='release-1.3.x'> </a>
-<h2 id='release13'>Releasing Apache Wicket 1.3.x</h2>
-<h3 id='building_the_release'>Building the release</h3>
+<h2 id='nexus'>Staging Releases using the Apache Nexus Repository</h2>
-<ul>
-<li>query dev@ for any open issues, it helps to look at JIRA first</li>
+<p>The key to stage and manage repositories on https://repository.apache.org are your Apache Commiter credentials.</p>
-<li>create tag, create release branch</li>
+<h3 id='staging_artifacts'>Staging Artifacts</h3>
-<li>check out release branch</li>
+<p>When you run <strong>mvn -P release deploy</strong> the generated artifacts will be uploaded into a Nexus staging repository.</p>
-<li>Set correct version in the pom files:</li>
+<p>Maven sends a username/password when attempting to upload the artifacts.</p>
-<li>Linux:</li>
-</ul>
-<div class='highlight'><pre><code class='console'><span class='go'>find . -name "pom.xml" | xargs sed -i -e "s/1.3-SNAPSHOT/1.3.2/g"</span>
-<span class='go'>find . -name "pom.xml" | xargs sed -i -e "s/wicket\/trunk/wicket\/releases\/wicket-1.3.3/g"</span>
-</code></pre>
-</div>
-<ul>
-<li>Mac OS X:</li>
-</ul>
-<div class='highlight'><pre><code class='console'><span class='go'>find . -name "pom.xml" | xargs sed -i "" -e "s/1.3-SNAPSHOT/1.3.2/g"</span>
-<span class='go'>find . -name "pom.xml" | xargs sed -i "" -e "s/wicket\/trunk/wicket\/releases\/wicket-1.3.3/g"</span>
+<p>The <code><id></code> of the staging repository is: <strong>apache.releases.https</strong>.</p>
+
+<p>Place a <code><server></code> definition in your <code>~/.m2/settings.xml</code> file like this:</p>
+<div class='highlight'><pre><code class='console'><span class='go'><?xml version="1.0"?></span>
+<span class='go'><settings></span>
+<span class='go'><servers></span>
+<span class='go'> <server></span>
+<span class='go'> <id>apache.releases.https</id></span>
+<span class='go'> <username>$username</username></span>
+<span class='go'> <password>$password</password></span>
+<span class='go'> </server></span>
+<span class='go'></servers></span>
+<span class='go'></settings></span>
</code></pre>
</div>
-<ul>
-<li>add JIRA generated release notes to CHANGELOG-1.3</li>
-
-<li>commit to release branch</li>
-
-<li>call release.sh</li>
+<p>This works if you can deploy artifacts into the repository.apache.org properly (i.e. you don’t see failures mentioning 401 errors).</p>
-<li>test the distribution (examples, rat, etc)</li>
+<h3 id='managing_staged_artifacts'>Managing Staged Artifacts</h3>
-<li>upload m2-repo and dist directory from target/ to p.a.o</li>
+<p>By logging in with your Apache committer credentials to https://repository.apache.org you can access the management interface for the staged artifacts.</p>
-<li>upload commons/KEY into dist folder on p.a.o</li>
+<p>The interface will allow you to:</p>
-<li>send vote message</li>
-
-<li>wait</li>
-
-<li>upload to mirrors (see below)</li>
+<ul>
+<li>View the staging repositories.</li>
-<li>release the version in JIRA</li>
+<li>Close staging repositories.</li>
-<li>wait 24 hours for mirrors to pick them up</li>
+<li>Release closed repository artifacts (into the release repo and after 1-2 hours into central as well).</li>
-<li>announce</li>
+<li>Drop open and closed staging repositories.</li>
</ul>
-<h2 id='mirrors'>Uploading to the mirror system</h2>
-<div class='highlight'><pre><code class='console'><span class='go'>ssh people.apache.org</span>
-<span class='go'>mkdir /www/www.apache.org/dist/wicket/1.4.0</span>
-<span class='go'>mv ~/public_html/wicket-1.4.0/dist/* /www/www.apache.org/dist/wicket/1.4.0</span>
-<span class='go'>chown -R :wicket /www/www.apache.org/dist/wicket/1.4.0</span>
-</code></pre>
-</div>
-<p><code>chown</code> is very important, if files do not have the wicket group they will not be copied to mirrors Apache guide to mirros: http://apache.org/dev/mirror-step-by-step.html</p>
-
-<p>It is a good idea to clean up older releases from /www/www.apache.org/dist/wicket/</p>
-
-<h2 id='mavencentral'>Uploading to maven repository</h2>
-
-<p>I haven’t got any really good way to put them in the maven mirrors. The problem is that right now we override the meta xml files, so only the latest version is listed. If we really should do this perfect we would modify meta files like /org/apache/wicket/wicket/maven-metadata.xml and add the version to it (as well as create the hashes again).</p>
-
-<p>But for now this is sufficient:</p>
-<div class='highlight'><pre><code class='console'><span class='go'>cd into the directory you have the artifacts which has been voted on.</span>
-<span class='go'>cp -R m2-repo/org/apache/wicket/* /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/wicket/</span>
-<span class='go'>chmod -R g+w * /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/wicket</span>
-</code></pre>
-</div>
-<p>Further reading: README under /www/people.apache.org/repo/m2-ibiblio-rsync-repository/</p>
+<p>More information is available at: <a href='http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven'>Publishing Maven Artifacts</a></p>
<h2 id='announcing'>Announcing the release</h2>
Modified: wicket/common/site/trunk/contribute/release.md
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/contribute/release.md?rev=1058436&r1=1058435&r2=1058436&view=diff
==============================================================================
--- wicket/common/site/trunk/contribute/release.md (original)
+++ wicket/common/site/trunk/contribute/release.md Thu Jan 13 07:35:31 2011
@@ -7,20 +7,38 @@ title: Build a release
* [Releasing Apache Wicket 1.4.x](#release-14)
* [Releasing Apache Wicket 1.3.x](#release-13)
-* [Uploading to the mirror system](#mirrors)
-* [Uploading to maven repository](#mavencentral)
+* [Staging Releases using the Apache Nexus Repository](#nexus)
* [Announcing the release](#announcing)
* [Additional tasks](#additional)
## Releasing Apache Wicket 1.4.x ## {#release-14}
-### Building the release ###
+### Building the Release ###
+
+#### Preparing #####
* Ask the dev@ mailing list if there are any issues that still need to be in the release (looking at JIRA is a good start)
+* Release the version in JIRA
* Assuming there are none, and you are now in build mode, update the CHANGELOG-1.4 file
- * you can use JIRA for this list: go to "releases", and under "unreleased", next to your version, there's a release notes link
+(you can use JIRA for this list: go to "releases", and under "unreleased", next to your version, there's a release notes link)
+
+Make sure your ```~/.m2/settings.xml``` contains the following definition
+
+{% highlight console %}
+<?xml version="1.0"?>
+<settings>
+<servers>
+ <server>
+ <id>apache.releases.https</id>
+ <username>$your_apache_username</username>
+ <password>$your_apache_password</password>
+ </server>
+</servers>
+</settings>
+{% endhighlight %}
+
* create a release branch to do your release work in (modifying poms, etc)
- * then checkout that release branch and cd into it
+* then checkout that release branch and cd into it
{% highlight console %}
$ svn cp https://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.x \
https://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.13 \
@@ -32,27 +50,29 @@ $ svn co https://svn.apache.org/repos/as
Checked out revision 1027818.
$ cd wicket-1.4.13
{% endhighlight %}
-* Set correct version in the pom files
- * Linux
-{% highlight console %}
-find . -name "pom.xml" | xargs sed -i -e "s/1.4-SNAPSHOT/1.4.13/g"
-find . -name "pom.xml" | xargs sed -i -e "s/wicket\/trunk/wicket\/releases\/wicket-1.4.13/g"
-{% endhighlight %}
- * Mac OS X
+* Set correct version in the pom files using the [maven-versions-plugin](http://mojo.codehaus.org/versions-maven-plugin):
{% highlight console %}
-find . -name "pom.xml" | xargs sed -i "" -e "s/1.4-SNAPSHOT/1.4.13/g"
-find . -name "pom.xml" | xargs sed -i "" -e "s/wicket\/trunk/wicket\/releases\/wicket-1.4.13/g"
-{% endhighlight %}
-* Commit these modified pom files to the release branch
-* Call release.sh (still from the checkout out release branch code)
- * NOTE: If you get an error while generating javadocs like "`java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl`", run a `mvn clean install -Dmaven.test.skip=true` followed by a `mvn javadoc:jar`, then re-run `release.sh`.
-* Test the distribution (examples, rat, etc)
-* Upload artifacts (including signing keys) to your people.apache.org account:
+mvn versions:set -DnewVersion=1.4.13
+... list of all changed artifacts changed.
+mvn versions:commit
+removes all of the pom.xml.versionsBackup files.
+{% endhighlight %}
+* Call release.sh (still from the checkout out release branch code) **NOTE** If you get an error while generating javadocs like "`java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl`", run a `mvn clean install -Dmaven.test.skip=true` followed by a `mvn javadoc:jar`, then re-run `release.sh`.
+* Login to the Apache Nexus Repository on http://repository.apache.org; See [Releasing with Apache Nexus](#nexus) below.
+* Select **Staging Repositories** from the left hand side, then select the repository and click **Close**.
+* Test that the distribution (examples, rat, etc) is accessible from the staging repository url.
+* upload non-maven artifacts to pao:
{% highlight console %}
+export wicketversion=<version>
svn export http://svn.apache.org/repos/asf/wicket/common/KEYS target/dist/KEYS
-ssh people.apache.org mkdir public_html/wicket-1.4.13
-scp -r target/dist target/m2-repo people.apache.org:public_html/wicket-1.4.13
+ssh people.apache.org mkdir public_html/wicket-$wicketversion
+scp -r target/dist target/m2-repo people.apache.org:public_html/wicket-$wicketversion
{% endhighlight %}
+* Commit these modified pom files to the release branch.
+* Send vote message to dev@ mailing list. Include link to the closed repository for testing against.
+* Wait requisite 72 hours for the vote to pass (we hope)
+* Login to repository.apache.org, select the closed repository and click **Release**. It will be accessible immediately through the apache release repo and then within 1-2 hours through maven central.
+* If the release is voted down you can **Drop** the staged release and then restage later after incorporating the necessary changes.
* Tag the release in SVN:
{% highlight console %}
$ svn cp https://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.13 \
@@ -60,77 +80,50 @@ https://svn.apache.org/repos/asf/wicket/
-m "tag release 1.4.13"
Committed revision 1027826.
{% endhighlight %}
-* Send vote message to dev@ mailing list
-* Wait requisite 72 hours for the vote to pass (we hope)
-* Upload to mirrors (see below)
-* Release the version in JIRA
-* Wait 24 hours for mirrors to pick them up
-* Announce (see below)
+* Wait until repo1.maven.org has picked up the release artifacts.
+* Wait 24 hours until mirrors picked up release artifacts
+* Announce (see [below](#announcing))
+## Staging Releases using the Apache Nexus Repository ## {#nexus}
-<a name="release-1.3.x"> </a>
-## Releasing Apache Wicket 1.3.x ## { #release13 }
+The key to stage and manage repositories on https://repository.apache.org are your Apache Commiter credentials.
-### Building the release ###
+### Staging Artifacts ###
-* query dev@ for any open issues, it helps to look at JIRA first
-* create tag, create release branch
-* check out release branch
-* Set correct version in the pom files:
-* Linux:
-{% highlight console %}
-find . -name "pom.xml" | xargs sed -i -e "s/1.3-SNAPSHOT/1.3.2/g"
-find . -name "pom.xml" | xargs sed -i -e "s/wicket\/trunk/wicket\/releases\/wicket-1.3.3/g"
-{% endhighlight %}
-* Mac OS X:
-{% highlight console %}
-find . -name "pom.xml" | xargs sed -i "" -e "s/1.3-SNAPSHOT/1.3.2/g"
-find . -name "pom.xml" | xargs sed -i "" -e "s/wicket\/trunk/wicket\/releases\/wicket-1.3.3/g"
-{% endhighlight %}
-* add JIRA generated release notes to CHANGELOG-1.3
-* commit to release branch
-* call release.sh
-* test the distribution (examples, rat, etc)
-* upload m2-repo and dist directory from target/ to p.a.o
-* upload commons/KEY into dist folder on p.a.o
-* send vote message
-* wait
-* upload to mirrors (see below)
-* release the version in JIRA
-* wait 24 hours for mirrors to pick them up
-* announce
+When you run **mvn -P release deploy** the generated artifacts will be uploaded into a Nexus staging repository.
-## Uploading to the mirror system ## {#mirrors}
+Maven sends a username/password when attempting to upload the artifacts.
-{% highlight console %}
-ssh people.apache.org
-mkdir /www/www.apache.org/dist/wicket/1.4.0
-mv ~/public_html/wicket-1.4.0/dist/* /www/www.apache.org/dist/wicket/1.4.0
-chown -R :wicket /www/www.apache.org/dist/wicket/1.4.0
-{% endhighlight %}
+The ```<id>``` of the staging repository is: **apache.releases.https**.
-`chown` is very important, if files do not have the wicket group they will not be copied to mirrors
-Apache guide to mirros: http://apache.org/dev/mirror-step-by-step.html
+Place a ```<server>``` definition in your ```~/.m2/settings.xml``` file like this:
-It is a good idea to clean up older releases from /www/www.apache.org/dist/wicket/
+{% highlight console %}
+<?xml version="1.0"?>
+<settings>
+<servers>
+ <server>
+ <id>apache.releases.https</id>
+ <username>$username</username>
+ <password>$password</password>
+ </server>
+</servers>
+</settings>
+{% endhighlight %}
-## Uploading to maven repository ## {#mavencentral}
+This works if you can deploy artifacts into the repository.apache.org properly (i.e. you don't see failures mentioning 401 errors).
-I haven't got any really good way to put them in the maven mirrors. The
-problem is that right now we override the meta xml files, so only the latest
-version is listed. If we really should do this perfect we would modify meta
-files like /org/apache/wicket/wicket/maven-metadata.xml and add the version to
-it (as well as create the hashes again).
+### Managing Staged Artifacts ###
-But for now this is sufficient:
+By logging in with your Apache committer credentials to https://repository.apache.org you can access the management interface for the staged artifacts.
-{% highlight console %}
-cd into the directory you have the artifacts which has been voted on.
-cp -R m2-repo/org/apache/wicket/* /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/wicket/
-chmod -R g+w * /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/wicket
-{% endhighlight %}
+The interface will allow you to:
+* View the staging repositories.
+* Close staging repositories.
+* Release closed repository artifacts (into the release repo and after 1-2 hours into central as well).
+* Drop open and closed staging repositories.
-Further reading: README under /www/people.apache.org/repo/m2-ibiblio-rsync-repository/
+More information is available at: [Publishing Maven Artifacts](http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven)
## Announcing the release ## {#announcing}