Author: buildbot
Date: Wed Apr 10 20:19:20 2013
New Revision: 858029
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 Wed Apr 10 20:19:20
2013
@@ -87,7 +87,7 @@
<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
+PATH=$PATH:/usr/local/bin/prince
</pre>
</div></div></li></ul>
