Author: buildbot
Date: Fri Feb  9 08:19:09 2018
New Revision: 1025107

Log:
Production update by buildbot for camel

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

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

Modified: websites/production/camel/content/camel-2210-release.html
==============================================================================
--- websites/production/camel/content/camel-2210-release.html (original)
+++ websites/production/camel/content/camel-2210-release.html Fri Feb  9 
08:19:09 2018
@@ -94,7 +94,7 @@
 <div style="min-height:200px">&#160;</div>
 
 
-<h2 id="Camel2.21.0Release-NewandNoteworthy">New and Noteworthy</h2><p>Welcome 
to the x.y.z release which approx XXX issues resolved (new features, 
improvements and bug fixes such as...)</p><ul><li>Upgraded to JAXB 2.3.0 which 
is more JDK9 compliant.</li><li>Added better support 
for&#160;<code>javax.jms.StreamMessage</code> types in&#160;<a shape="rect" 
href="jms.html">JMS</a> component.</li><li>Optimised&#160;<a shape="rect" 
href="jms.html">JMS</a> to support ActiveMQ Artemis <a shape="rect" 
class="external-link" 
href="http://activemq.apache.org/artemis/docs/latest/large-messages.html";>large 
messages</a> so you can send and receive big messages such as GB's in size. 
There is an example demonstrating this in 
camel-example-artemis-large-messages.</li><li>Added support for route coverage 
reports which allows 3rd party tooling via SPI to visualise route coverage to 
Camel developers.</li><li>Added route-coverage goal to the <a shape="rect" 
class="external-link" href="https://github.com/
 
apache/camel/blob/master/tooling/maven/camel-maven-plugin/src/main/docs/camel-maven-plugin.adoc"
 rel="nofollow">Camel Maven Plugin</a> so you can report route coverage from 
Maven command line.</li><li>Added support for doing manual commits via Java 
code when using <a shape="rect" href="kafka.html">Kafka</a> 
consumer.</li><li>Vendor extensions in the swagger generated API docs is now 
disabled turned off, when using&#160;<a shape="rect" href="rest-dsl.html">Rest 
DSL</a>&#160;(not all 3rd party&#160;API gateways/tooling support vendor 
extensions). You can turn this back-on via the apiVendorExtension 
option.</li><li>The SFTP consumer now also supports 
the&#160;<code>useList</code> option which can be used to download a single 
known file without use LIST operation on the FTP server (which can be slow if 
the FTP server has many files in the LIST results)</li><li>Camel&#160;<a 
shape="rect" href="json.html">JSON</a> with camel-jackson will now automatic 
use shared ObjectMapper instance if t
 here is only one instance in the&#160;<a shape="rect" 
href="registry.html">Registry</a>. For example users with Spring Boot then 
allows Camel to easily use the default mapper from Spring 
Boot.</li><li>Added&#160;<code>ExtendedStartupListener</code> that allows a 
callback just after the CamelContext has been fully started.</li><li>You can 
now specify examples in the&#160;<a shape="rect" href="rest-dsl.html">Rest 
DSL</a> that are included in the generated Swagger api-doc via 
camel-swagger-java.</li><li>Improved file/ftp consumer to use current thread to 
poll, instead of a scheduled background task, when using pollEnrich (<a 
shape="rect" href="content-enricher.html">Content Enricher</a>).</li><li><a 
shape="rect" href="direct.html">Direct</a> component now blocks by default if 
sending to a consumer which is not yet ready, which may happen during startup 
(little window of opportunity). This 
avoids&#160;<code>DirectConsumerNotAvailableException</code> being thrown 
during startup etc.</li>
 <li>The&#160;<a shape="rect" href="ftp.html">FTP</a> component can now log 
progress (turn on&#160;transferLoggingLevel) when perfomring download/upload 
and other operations. You can also find this information for the consumer in 
JMX.&#160;</li><li>Added support for resuming downloads to&#160;<a shape="rect" 
href="ftp.html">FTP</a> component. For example if you download big files and 
has connection problems with the FTP server. Then later when the connectivity 
works again, Camel can resume download the in-progress 
file.</li><li>The&#160;<a shape="rect" 
href="jetty.html">Jetty</a>&#160;and&#160;<a shape="rect" 
href="servlet.html">SERVLET</a> consumers will now return HTTP Status 405 
(method not allowed) for requests that would have been processed by another 
HTTP request method, for example calling REST services with the wrong method. 
Beforehand a 404 error code was always regardless.</li><li>Reworked 
the&#160;<code>FileIdempotentRepository</code> so the internal in-memory cache 
is onl
 y used for quick lookup of the most frequent file names, and lookup from disk 
as well. See more details in the class javadoc of the file.</li></ul><p>The 
following issues has been fixed</p><ul><li>Fixed&#160;afterApplicationStart 
callback on camel-spring-boot to be called later and after CamelContext has 
been fully started.</li><li>Fixed an issue testing with&#160;@UseAdviceWith and 
Camel on Spring Boot.</li><li>Fixed&#160;<a shape="rect" 
href="oncompletion.html">OnCompletion</a> would not be triggered from a route 
using&#160;<a shape="rect" href="splitter.html">Splitter</a> and an exception 
was thrown during splitting.</li><li>Fixed&#160;<a shape="rect" 
href="kafka.html">Kafka</a> consumer&#160;stops consuming messages when 
exception occurs during offset commit.</li><li>Fixed&#160;<a shape="rect" 
href="netty4.html">Netty4</a> consumer to stop taking in new requests while 
being shutdown, as otherwise it cannot graceful shutdown if new requests come 
in faster than it can process exis
 ting in-flight messages.</li><li>Fixed an issue with&#160;<a shape="rect" 
href="routing-slip.html">Routing Slip</a> and&#160;<a shape="rect" 
href="dynamic-router.html">Dynamic Router</a> when using context scoped error 
handler, could cause the error handler to become stopped.</li><li>Fixed&#160;<a 
shape="rect" href="rest-dsl.html">Rest DSL</a> with&#160;<a shape="rect" 
href="jetty.html">Jetty</a> security via custom define security handler and 
turned on api-doc as well would not startup Jetty server due missing 
NoLoginService error.</li></ul><h3 id="Camel2.21.0Release-New">New <a 
shape="rect" href="enterprise-integration-patterns.html">Enterprise Integration 
Patterns</a></h3><ul><li><a shape="rect" class="external-link" 
href="https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/claimCheck-eip.adoc";
 rel="nofollow">Claim Check EIP</a> with push/pop functionality.</li><li><a 
shape="rect" class="external-link" 
href="https://github.com/apache/camel/blob/master/camel-
 core/src/main/docs/eips/saga-eip.adoc" rel="nofollow">Saga EIP</a> for 
simulation transactionals in distributed systems</li></ul><h3 
id="Camel2.21.0Release-New.1">New <a shape="rect" 
href="components.html">Components</a></h3><ul><li>camel-aws - MQ component for 
working with Amazon MQ</li><li>camel-elasticsearch5-rest -&#160;The 
elasticsearch component is used for interfacing with ElasticSearch server using 
5.x REST API.</li><li>camel-yql -&#160;The YQL (Yahoo! Query Language) platform 
enables you to query, filter, and combine data across the 
web.</li><li>camel-wordpres - To integrate Camel with Wordpres</li></ul><h3 
id="Camel2.21.0Release-NewDataFormats">New <a shape="rect" 
href="data-format.html">Data Formats</a></h3><h3 
id="Camel2.21.0Release-New.2">New <a shape="rect" 
href="languages.html">Languages</a></h3><h2 
id="Camel2.21.0Release-APIbreaking">API breaking</h2><ul><li>Minor API changes 
to&#160;<code>org.apache.camel.component.file.GenericFileOperations</code></li><li>Minor
 API
  changes 
to&#160;<code>org.apache.camel.http.common.ServletResolveConsumerStrategy</code></li><li><code>All
 the AwsEndpoint uri options have been removed: since we are now using AWS 
client builders, the way we were using the endpoint cannot be used anymore, 
since clients are immutable now. If you still need to set an AWS endpoint on 
your client, you can create your client instance and put it in the Camel 
registry.</code></li></ul><h2 id="Camel2.21.0Release-KnownIssues">Known 
Issues</h2><h2 
id="Camel2.21.0Release-Importantchangestoconsiderwhenupgrading">Important 
changes to consider when upgrading</h2><ul><li>Jetty has been upgraded to 9.4 
by default, and camel-jetty is requring version 9.3 or 9.4 to run in 
OSGi.</li><li><a shape="rect" href="direct.html">Direct</a> component now 
blocks by default if sending to a consumer which is not yet ready, which may 
happen during startup (little window of opportunity). This 
avoids&#160;<code>DirectConsumerNotAvailableException</code>&#160;being
  thrown during startup etc. The old beavhaior can be turned on by 
setting&#160;<code>block=false</code> on the direct component level, or on 
endpoints where needed.</li><li>When using&#160;<code>camel-saxon</code> then 
the SaxonXpathFactory class is created in the <a shape="rect" 
class="external-link" 
href="https://www.saxonica.com/html/documentation/xpath-api/jaxp-xpath/factory.html";
 rel="nofollow">recommended way</a> from Saxon. It will fallback and create the 
factory the old way if not 
possible.</li><li>The&#160;<code>camel-json-validator</code> component has 
switched from using Everit to NetworkNT JSon Schema validator library, as the 
former had ASF license implications and would not be allowed in future Camel 
releases. The NetworkNT supports v4 draft of JSon Schema as validation so make 
sure to use that draft version in your schemas.</li><li>Reworked 
the&#160;<code>FileIdempotentRepository</code>&#160;so the internal in-memory 
cache is only used for quick lookup of the most fre
 quent file names, and lookup from disk as well. See more details in the class 
javadoc of the file.</li><li>The&#160;<a shape="rect" 
href="karaf.html">Karaf</a>&#160;commands for routes is changed so the 
arguments for the camel context is first, and the route id is the 2nd argument. 
This allows the route completer to use the selected camel context name to only 
show route ids from that camel context, as otherwise it shows all the routes 
for every Camel application running in Karaf.</li></ul><h2 
id="Camel2.21.0Release-GettingtheDistributions">Getting the 
Distributions</h2><h3 id="Camel2.21.0Release-BinaryDistributions">Binary 
Distributions</h3><div class="table-wrap"><table 
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" 
class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" 
class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" 
class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td 
colspan="1" rowspan="1" class="c
 onfluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><a shape="rect" class="external-link" 
href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/x.y.x/apache-camel-x.y.x.zip";>apache-camel-x.y.x.zip</a></p></td><td
 colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" 
class="external-link" 
href="http://www.apache.org/dist/camel/apache-camel/x.y.x/apache-camel-x.y.x.zip.asc";>apache-camel-x.y.x.zip.asc</a></p></td></tr><tr><td
 colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin 
Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a 
shape="rect" class="external-link" 
href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/x.y.x/apache-camel-x.y.x.tar.gz";>apache-camel-x.y.x.tar.gz</a></p></td><td
 colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" 
class="external-link" 
href="http://www.apache.org/dist/camel/apache-camel/x.y.x/apache-camel-x.y.x.tar.gz.asc";>apache-camel-x.y.x
 .tar.gz.asc</a></p></td></tr></tbody></table></div><div 
class="confluence-information-macro 
confluence-information-macro-information"><p class="title">The above URLs use 
redirection</p><span class="aui-icon aui-icon-small aui-iconfont-info 
confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><p>The above URLs use the Apache 
Mirror system to redirect you to a suitable mirror for your download. Some 
users have experienced issues with some versions of browsers (e.g. some Safari 
browsers). If the download doesn't seem to work for you from the above URL then 
try using <a shape="rect" class="external-link" 
href="http://www.mozilla.com/en-US/firefox/"; 
rel="nofollow">FireFox</a></p></div></div><h3 
id="Camel2.21.0Release-SourceDistributions">Source Distributions</h3><div 
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" 
rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" 
rowspan="1" class="confluenceTh"><p>Dow
 nload Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP 
Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>Source (zip)</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><a shape="rect" class="external-link" 
href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/x.y.x/apache-camel-x.y.x-src.zip";>apache-camel-x.y.x-src.zip</a></p></td><td
 colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" 
class="external-link" 
href="http://www.apache.org/dist/camel/apache-camel/x.y.x/apache-camel-x.y.x-src.zip.asc";>apache-camel-x.y.x-src.zip.asc</a></p></td></tr></tbody></table></div><h3
 id="Camel2.21.0Release-GettingtheBinariesusingMaven2">Getting the Binaries 
using Maven 2</h3><p>To use this release in your maven project, the proper 
dependency configuration that you should use in your <a shape="rect" 
class="external-link" 
href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html";>Maven
  POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
+<h2 id="Camel2.21.0Release-NewandNoteworthy">New and Noteworthy</h2><p>Welcome 
to the x.y.z release which approx XXX issues resolved (new features, 
improvements and bug fixes such as...)</p><ul><li>Upgraded to JAXB 2.3.0 which 
is more JDK9 compliant.</li><li>Added better support 
for&#160;<code>javax.jms.StreamMessage</code> types in&#160;<a shape="rect" 
href="jms.html">JMS</a> component.</li><li>Optimised&#160;<a shape="rect" 
href="jms.html">JMS</a> to support ActiveMQ Artemis <a shape="rect" 
class="external-link" 
href="http://activemq.apache.org/artemis/docs/latest/large-messages.html";>large 
messages</a> so you can send and receive big messages such as GB's in size. 
There is an example demonstrating this in 
camel-example-artemis-large-messages.</li><li>Added support for route coverage 
reports which allows 3rd party tooling via SPI to visualise route coverage to 
Camel developers.</li><li>Added route-coverage goal to the <a shape="rect" 
class="external-link" href="https://github.com/
 
apache/camel/blob/master/tooling/maven/camel-maven-plugin/src/main/docs/camel-maven-plugin.adoc"
 rel="nofollow">Camel Maven Plugin</a> so you can report route coverage from 
Maven command line.</li><li>Added support for doing manual commits via Java 
code when using <a shape="rect" href="kafka.html">Kafka</a> 
consumer.</li><li>Vendor extensions in the swagger generated API docs is now 
disabled turned off, when using&#160;<a shape="rect" href="rest-dsl.html">Rest 
DSL</a>&#160;(not all 3rd party&#160;API gateways/tooling support vendor 
extensions). You can turn this back-on via the apiVendorExtension 
option.</li><li>The SFTP consumer now also supports 
the&#160;<code>useList</code> option which can be used to download a single 
known file without use LIST operation on the FTP server (which can be slow if 
the FTP server has many files in the LIST results)</li><li>Camel&#160;<a 
shape="rect" href="json.html">JSON</a> with camel-jackson will now automatic 
use shared ObjectMapper instance if t
 here is only one instance in the&#160;<a shape="rect" 
href="registry.html">Registry</a>. For example users with Spring Boot then 
allows Camel to easily use the default mapper from Spring 
Boot.</li><li>Added&#160;<code>ExtendedStartupListener</code> that allows a 
callback just after the CamelContext has been fully started.</li><li>You can 
now specify examples in the&#160;<a shape="rect" href="rest-dsl.html">Rest 
DSL</a> that are included in the generated Swagger api-doc via 
camel-swagger-java.</li><li>Improved file/ftp consumer to use current thread to 
poll, instead of a scheduled background task, when using pollEnrich (<a 
shape="rect" href="content-enricher.html">Content Enricher</a>).</li><li><a 
shape="rect" href="direct.html">Direct</a> component now blocks by default if 
sending to a consumer which is not yet ready, which may happen during startup 
(little window of opportunity). This 
avoids&#160;<code>DirectConsumerNotAvailableException</code> being thrown 
during startup etc.</li>
 <li>The&#160;<a shape="rect" href="ftp.html">FTP</a> component can now log 
progress (turn on&#160;transferLoggingLevel) when perfomring download/upload 
and other operations. You can also find this information for the consumer in 
JMX.&#160;</li><li>Added support for resuming downloads to&#160;<a shape="rect" 
href="ftp.html">FTP</a> component. For example if you download big files and 
has connection problems with the FTP server. Then later when the connectivity 
works again, Camel can resume download the in-progress 
file.</li><li>The&#160;<a shape="rect" 
href="jetty.html">Jetty</a>&#160;and&#160;<a shape="rect" 
href="servlet.html">SERVLET</a> consumers will now return HTTP Status 405 
(method not allowed) for requests that would have been processed by another 
HTTP request method, for example calling REST services with the wrong method. 
Beforehand a 404 error code was always regardless.</li><li>Reworked 
the&#160;<code>FileIdempotentRepository</code> so the internal in-memory cache 
is onl
 y used for quick lookup of the most frequent file names, and lookup from disk 
as well. See more details in the class javadoc of the file.</li><li>The&#160;<a 
shape="rect" href="sql-stored-procedure.html">SQL Stored Procedure</a> 
component now supports INOUT parameters.</li></ul><p>The following issues has 
been fixed</p><ul><li>Fixed&#160;afterApplicationStart callback on 
camel-spring-boot to be called later and after CamelContext has been fully 
started.</li><li>Fixed an issue testing with&#160;@UseAdviceWith and Camel on 
Spring Boot.</li><li>Fixed&#160;<a shape="rect" 
href="oncompletion.html">OnCompletion</a> would not be triggered from a route 
using&#160;<a shape="rect" href="splitter.html">Splitter</a> and an exception 
was thrown during splitting.</li><li>Fixed&#160;<a shape="rect" 
href="kafka.html">Kafka</a> consumer&#160;stops consuming messages when 
exception occurs during offset commit.</li><li>Fixed&#160;<a shape="rect" 
href="netty4.html">Netty4</a> consumer to stop taking in
  new requests while being shutdown, as otherwise it cannot graceful shutdown 
if new requests come in faster than it can process existing in-flight 
messages.</li><li>Fixed an issue with&#160;<a shape="rect" 
href="routing-slip.html">Routing Slip</a> and&#160;<a shape="rect" 
href="dynamic-router.html">Dynamic Router</a> when using context scoped error 
handler, could cause the error handler to become stopped.</li><li>Fixed&#160;<a 
shape="rect" href="rest-dsl.html">Rest DSL</a> with&#160;<a shape="rect" 
href="jetty.html">Jetty</a> security via custom define security handler and 
turned on api-doc as well would not startup Jetty server due missing 
NoLoginService error.</li></ul><h3 id="Camel2.21.0Release-New">New <a 
shape="rect" href="enterprise-integration-patterns.html">Enterprise Integration 
Patterns</a></h3><ul><li><a shape="rect" class="external-link" 
href="https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/claimCheck-eip.adoc";
 rel="nofollow">Claim Check EIP</a>
  with push/pop functionality.</li><li><a shape="rect" class="external-link" 
href="https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/saga-eip.adoc";
 rel="nofollow">Saga EIP</a> for simulation transactionals in distributed 
systems</li></ul><h3 id="Camel2.21.0Release-New.1">New <a shape="rect" 
href="components.html">Components</a></h3><ul><li>camel-aws - MQ component for 
working with Amazon MQ</li><li>camel-elasticsearch5-rest -&#160;The 
elasticsearch component is used for interfacing with ElasticSearch server using 
5.x REST API.</li><li>camel-yql -&#160;The YQL (Yahoo! Query Language) platform 
enables you to query, filter, and combine data across the 
web.</li><li>camel-wordpres - To integrate Camel with Wordpres</li></ul><h3 
id="Camel2.21.0Release-NewDataFormats">New <a shape="rect" 
href="data-format.html">Data Formats</a></h3><h3 
id="Camel2.21.0Release-New.2">New <a shape="rect" 
href="languages.html">Languages</a></h3><h2 
id="Camel2.21.0Release-APIbreaking">API
  breaking</h2><ul><li>Minor API changes 
to&#160;<code>org.apache.camel.component.file.GenericFileOperations</code></li><li>Minor
 API changes 
to&#160;<code>org.apache.camel.http.common.ServletResolveConsumerStrategy</code></li><li><code>All
 the AwsEndpoint uri options have been removed: since we are now using AWS 
client builders, the way we were using the endpoint cannot be used anymore, 
since clients are immutable now. If you still need to set an AWS endpoint on 
your client, you can create your client instance and put it in the Camel 
registry.</code></li></ul><h2 id="Camel2.21.0Release-KnownIssues">Known 
Issues</h2><h2 
id="Camel2.21.0Release-Importantchangestoconsiderwhenupgrading">Important 
changes to consider when upgrading</h2><ul><li>Jetty has been upgraded to 9.4 
by default, and camel-jetty is requring version 9.3 or 9.4 to run in 
OSGi.</li><li><a shape="rect" href="direct.html">Direct</a> component now 
blocks by default if sending to a consumer which is not yet ready, which ma
 y happen during startup (little window of opportunity). This 
avoids&#160;<code>DirectConsumerNotAvailableException</code>&#160;being thrown 
during startup etc. The old beavhaior can be turned on by 
setting&#160;<code>block=false</code> on the direct component level, or on 
endpoints where needed.</li><li>When using&#160;<code>camel-saxon</code> then 
the SaxonXpathFactory class is created in the <a shape="rect" 
class="external-link" 
href="https://www.saxonica.com/html/documentation/xpath-api/jaxp-xpath/factory.html";
 rel="nofollow">recommended way</a> from Saxon. It will fallback and create the 
factory the old way if not 
possible.</li><li>The&#160;<code>camel-json-validator</code> component has 
switched from using Everit to NetworkNT JSon Schema validator library, as the 
former had ASF license implications and would not be allowed in future Camel 
releases. The NetworkNT supports v4 draft of JSon Schema as validation so make 
sure to use that draft version in your schemas.</li><li>Rework
 ed the&#160;<code>FileIdempotentRepository</code>&#160;so the internal 
in-memory cache is only used for quick lookup of the most frequent file names, 
and lookup from disk as well. See more details in the class javadoc of the 
file.</li><li>The&#160;<a shape="rect" 
href="karaf.html">Karaf</a>&#160;commands for routes is changed so the 
arguments for the camel context is first, and the route id is the 2nd argument. 
This allows the route completer to use the selected camel context name to only 
show route ids from that camel context, as otherwise it shows all the routes 
for every Camel application running in Karaf.</li></ul><h2 
id="Camel2.21.0Release-GettingtheDistributions">Getting the 
Distributions</h2><h3 id="Camel2.21.0Release-BinaryDistributions">Binary 
Distributions</h3><div class="table-wrap"><table 
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" 
class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" 
class="confluenceTh"><p>Download Link</p></th><th 
 colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of 
download</p></th></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" 
href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/x.y.x/apache-camel-x.y.x.zip";>apache-camel-x.y.x.zip</a></p></td><td
 colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" 
class="external-link" 
href="http://www.apache.org/dist/camel/apache-camel/x.y.x/apache-camel-x.y.x.zip.asc";>apache-camel-x.y.x.zip.asc</a></p></td></tr><tr><td
 colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin 
Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a 
shape="rect" class="external-link" 
href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/x.y.x/apache-camel-x.y.x.tar.gz";>apache-camel-x.y.x.tar.gz</a></p></td><td
 colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rec
 t" class="external-link" 
href="http://www.apache.org/dist/camel/apache-camel/x.y.x/apache-camel-x.y.x.tar.gz.asc";>apache-camel-x.y.x.tar.gz.asc</a></p></td></tr></tbody></table></div><div
 class="confluence-information-macro 
confluence-information-macro-information"><p class="title">The above URLs use 
redirection</p><span class="aui-icon aui-icon-small aui-iconfont-info 
confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><p>The above URLs use the Apache 
Mirror system to redirect you to a suitable mirror for your download. Some 
users have experienced issues with some versions of browsers (e.g. some Safari 
browsers). If the download doesn't seem to work for you from the above URL then 
try using <a shape="rect" class="external-link" 
href="http://www.mozilla.com/en-US/firefox/"; 
rel="nofollow">FireFox</a></p></div></div><h3 
id="Camel2.21.0Release-SourceDistributions">Source Distributions</h3><div 
class="table-wrap"><table class="confluenceTable"><tbody
 ><tr><th colspan="1" rowspan="1" 
 >class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" 
 >class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" 
 >class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td 
 >colspan="1" rowspan="1" class="confluenceTd"><p>Source (zip)</p></td><td 
 >colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" 
 >class="external-link" 
 >href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/x.y.x/apache-camel-x.y.x-src.zip";>apache-camel-x.y.x-src.zip</a></p></td><td
 > colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" 
 >class="external-link" 
 >href="http://www.apache.org/dist/camel/apache-camel/x.y.x/apache-camel-x.y.x-src.zip.asc";>apache-camel-x.y.x-src.zip.asc</a></p></td></tr></tbody></table></div><h3
 > id="Camel2.21.0Release-GettingtheBinariesusingMaven2">Getting the Binaries 
 >using Maven 2</h3><p>To use this release in your maven project, the proper 
 >dependency configuration that you should use
  in your <a shape="rect" class="external-link" 
href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html";>Maven
 POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
   &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
   &lt;artifactId&gt;camel-core&lt;/artifactId&gt;


Reply via email to