camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r849333 - in /websites/production/camel/content: cache/main.pageCache release-guide.html
Date Mon, 04 Feb 2013 13:18:21 GMT
Author: buildbot
Date: Mon Feb  4 13:18:21 2013
New Revision: 849333

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/release-guide.html

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/release-guide.html
==============================================================================
--- websites/production/camel/content/release-guide.html (original)
+++ websites/production/camel/content/release-guide.html Mon Feb  4 13:18:21 2013
@@ -84,16 +84,12 @@
 <h2><a shape="rect" name="ReleaseGuide-Prerequisites"></a>Prerequisites</h2>
 
 <p>To prepare or perform a release you MUST BE at least an Apache Camel committer.</p>
-<ul><li>artifacts for each and every release must be SIGNED; your public key
should be added to the KEYS file</li><li>your public key must also be cross-signed
by other Apache committers (this can be done at key signing parties at ApacheCon for instance)</li><li>make
sure you have the correct maven configuration in <tt>~/.m2/settings.xml</tt></li><li>use
Maven 2.2.1+ (Maven 2.1.x is known to produce wrong gpg pom signatures - <a shape="rect"
class="external-link" href="http://jira.codehaus.org/browse/MGPG-14" rel="nofollow">MGPG-14</a>)
-	<ul><li>from Camel 2.10 onwards we will require to use Maven 3.0.x+</li></ul>
-	</li><li>you may want to get familiar with the release settings in the parent
apache POM.</li><li>make sure you have installed <a shape="rect" class="external-link"
href="http://www.princexml.com/" rel="nofollow">princexml</a> to be able to generate
the Camel manual
-	<ul><li>Add the bin directory to your path variable
+<ul><li>The artifacts for each and every release must be SIGNED; your public
key should be added to the KEYS file</li><li>Your public key must also be cross-signed
by other Apache committers (this can be done at key signing parties at ApacheCon for instance)</li><li>Make
sure you have the correct maven configuration in <tt>~/.m2/settings.xml</tt></li><li>Use
Maven 2.2.1+ (Maven 2.1.x is known to produce wrong gpg pom signatures - <a shape="rect"
class="external-link" href="http://jira.codehaus.org/browse/MGPG-14" rel="nofollow">MGPG-14</a>)</li><li>From
Camel 2.10 onwards we will require to use Maven 3.0.2+</li><li>From Camel 2.11
onwards we will require to use Maven 3.0.4+</li><li>You may want to get familiar
with the release settings in the parent apache POM.</li><li>Make sure you have
installed <a shape="rect" class="external-link" href="http://www.princexml.com/" rel="nofollow">Prince</a>
to be able to generate the Camel manual</li><li>Add your Prince installation <tt>bi
 n</tt> directory to your <tt>PATH</tt> variable:
 <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
 <pre class="code-java">
 PATH=$PATH:/usr/local/lib/prince/bin
 </pre>
 </div></div></li></ul>
-	</li></ul>
 
 
 <h2><a shape="rect" name="ReleaseGuide-Maven2Setup"></a>Maven 2 Setup</h2>



Mime
View raw message