Author: buildbot
Date: Fri Feb 21 10:18:48 2014
New Revision: 898757
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 Fri Feb 21 10:18:48
2014
@@ -86,7 +86,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h1
id="ReleaseGuide-HowtocreateandannounceaCamelrelease.">How to create and
announce a Camel release.</h1><p>This release guide is based on the <a
shape="rect" class="external-link"
href="http://maven.apache.org/developers/release/apache-release.html";>General
guide for releasing Maven-based projects at Apache</a>, so be sure to check it
out before continuing and meet all prerequisites.</p><p><strong>Note</strong>:
Make sure that you are using <strong>JDK 6</strong>. However for releasing
Camel 2.12.0 onwards better use <strong>JDK 7</strong>, this for the sake of
the new <a shape="rect" class="external-link"
href="http://camel.apache.org/endpoint-annotations.html";>HTML documentation
feature</a> which doesn't work properly because of misbehaving annotation
processing in <strong>JDK 6</strong>.</p><h2
id="ReleaseGuide-Prerequisites">Prerequisites</h2><p>To prepare or perform a
release you MUST BE at least an Apache Camel committer.</p><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
<code>~/.m2/settings.xml</code></li><li>From Camel 2.10 onwards we will require
to use Maven [3.0.2,3.1.0)</li><li>From Camel 2.11 onwards we will require to
use Maven [3.0.4,3.1.0]</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><p>Add your Prince installation <code>bin</code> directory to
your <code>PATH</code> variable:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h1
id="ReleaseGuide-HowtocreateandannounceaCamelrelease.">How to create and
announce a Camel release.</h1><p>This release guide is based on the <a
shape="rect" class="external-link"
href="http://maven.apache.org/developers/release/apache-release.html";>General
guide for releasing Maven-based projects at Apache</a>, so be sure to check it
out before continuing and meet all prerequisites.</p><p><span style="font-size:
20.0px;line-height: 1.5;">Prerequisites</span></p><p>To prepare or perform a
release you MUST BE at least an Apache Camel committer.</p><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
<code>~/.m2/settings.xml</code></li><li>From Camel 2.10 onwards we will require
to
use Maven [3.0.2,3.1.0)</li><li>From Camel 2.11 onwards we will require to
use Maven [3.0.4,3.1.0]</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><p>Add your Prince installation <code>bin</code> directory to
your <code>PATH</code> variable:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: text; gutter: false"
type="syntaxhighlighter"><![CDATA[PATH=$PATH:/usr/local/bin/prince
]]></script>
</div></div></li></ul><h2 id="ReleaseGuide-Maven2Setup">Maven 2
Setup</h2><p>Before you deploy anything to the maven repository using Maven 2,
you should configure your ~/.m2/settings.xml file so that the file permissions
of the deployed artifacts are group writable. If you do not do this, other
developers will not able to overwrite your SNAPSHOT releases with newer
versions. The settings follow the <a shape="rect" class="external-link"
href="http://maven.apache.org/developers/committer-settings.html";>guidelines
</a> used by the Maven project. Please pay particular attention to the <a
shape="rect" class="external-link"
href="http://maven.apache.org/guides/mini/guide-encryption.html";>password
encryption recommendations</a>.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
