Modified: websites/production/camel/content/camel-2180-release.html
==============================================================================
--- websites/production/camel/content/camel-2180-release.html (original)
+++ websites/production/camel/content/camel-2180-release.html Tue Jul 26 
10:18:57 2016
@@ -85,7 +85,7 @@
        <tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h1 
id="Camel2.18.0Release-Camel2.18.0release(currentlyinprogress)">Camel 2.18.0 
release (currently in progress)</h1><div 
style="padding-right:20px;float:left;margin-left:-20px;"><p><span 
class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image 
confluence-external-resource" 
src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png"; 
data-image-src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png";></span></p></div><div
 style="min-height:200px">&#160;</div><h2 
id="Camel2.18.0Release-NewandNoteworthy">New and Noteworthy</h2><p>Welcome to 
the 2.18.0 release which approx XXX issues resolved (new features, improvements 
and bug fixes such as...)</p><ul><li>All Camel&#160;<a shape="rect" 
href="components.html">Components</a> that has options to be configured now 
supports and include&#160;<a shape="rect" href="spring-boot.html">Spring 
Boot</a>&#160;auto configuration for those options, so they can easily 
 be configured in your application.yaml file when using Spring Boot with 
Camel.&#160;</li><li>Camel <a shape="rect" href="spring-boot.html">Spring 
Boot</a> now supports the same&#160;<a shape="rect" 
href="advanced-configuration-of-camelcontext-using-spring.html">advanced 
configuration</a>&#160;you can do with Spring XML, if the beans&#160;have been 
configured using&#160;<code>@Bean</code>&#160;style in a Spring Boot 
configuration class.</li><li>Added <a shape="rect" 
href="hystrix-eip.html">Hystrix EIP</a> as EIP pattern that uses native 
Netflixx Hystrix as the Circuit Breaker implementation.&#160;This requires 
having&#160;<code>camel-hystrix</code>&#160;on the 
classpath.</li><li>Added&#160;<a shape="rect" 
href="servicecall-eip.html">Service Call EIP</a> as EIP pattern that allows to 
call a remote service in a distributed system, where the service is looked up 
from a service registry of some sorts, such as kubernetes, consul, etcd, 
zookeeper etc.</li><li><span style="line-height: 1.42
 857;">Running Camel with&#160;<a shape="rect" href="spring-boot.html">Spring 
Boot</a> now includes a Camel Health Indicator (actuator) if 
<code>spring-boot-starter-actuator</code>&#160;is on the 
classpath.</span></li><li>Spring-DM for OSGi moved out of camel-spring into a 
separate camel-spring-dm module.<span style="line-height: 1.42857;"><br 
clear="none"></span></li><li><span style="line-height: 1.42857;">Improved 
the&#160;</span><a shape="rect" href="bean.html">Bean</a><span 
style="line-height: 1.42857;"> component to better match method parameter types 
when using&#160;</span><a shape="rect" href="simple.html">Simple</a><span 
style="line-height: 1.42857;"> language as parameter 
values.</span></li><li>Added&#160;<code>BindyConverter</code> that allows to 
implement custom data converters for&#160;<a shape="rect" 
href="bindy.html">Bindy</a></li><li>The access in the&#160;<a shape="rect" 
href="rest-dsl.html">Rest DSL</a> has been deprecated and no longer in use - 
its not part of swagg
 er specification anymore.</li><li><a shape="rect" 
href="nats.html">Camel-NATS</a>&#160;now uses JNATS client instead of the 
deprecated Java_nats one.</li><li>During startup of&#160;<a shape="rect" 
href="camelcontext.html">CamelContext</a> the services that are used as part of 
routes are now deferred being started to the end of the startup process. Some 
IoC frameworks like Spring can otherwise causes a circular dependency issue if 
services are started too early. A side effect is that if service startup 
failures happen when being started later, they are now wrapped in the 
<code>FailedToStartupRouteException</code> to better pin point which route thas 
the problem.</li><li>Improved the startup sequence of&#160;<a shape="rect" 
href="spring-java-config.html">Spring Java Config</a> to be similar to&#160;<a 
shape="rect" href="spring-boot.html">Spring Boot</a> that helps prevent Spring 
initialization errors about circular dependencies issues.</li><li>Added PATCH 
to&#160;<a shape="rect" href=
 "rest-dsl.html">Rest DSL</a></li><li>Added "starts with" and "ends with" 
operator to the <a shape="rect" 
href="simple.html">Simple</a>&#160;language.</li><li>Added&#160;<code>BeanIOSplitter</code>
 to&#160;<a shape="rect" href="beanio.html">BeanIO</a> that can be used with 
the&#160;<a shape="rect" href="splitter.html">Splitter</a> EIP to split big 
payloads in streaming mode without reading the entire content into 
memory.</li><li>Some of the <a shape="rect" 
href="aws.html">AWS</a>&#160;components allows to specify ARN in the endpoint 
configuration.&#160;</li><li>The create operation in&#160;<a shape="rect" 
href="zookeeper.html">Zookeeper</a> now creates sub paths if 
missing.</li><li>Added support for async mode for&#160;<a shape="rect" 
href="servlet.html">SERVLET</a> component to leverage Asynchronous Servlet from 
the Servlet 3.0 spec.</li><li><a shape="rect" 
href="bean.html">Bean</a>&#160;component and <a shape="rect" 
href="bean-language.html">Bean Language</a>&#160;validates method 
 name must be a valid according to java identifier rules, and also if parameter 
syntax has an ending parenthesis.</li><li>You can now 
use&#160;<code>@RunWith(CamelSpringBootJUnit4ClassRunner.class)</code> to test 
Camel&#160;<a shape="rect" href="spring-boot.html">Spring 
Boot</a>&#160;applications and use the Camel test annotations from&#160;<a 
shape="rect" href="spring-testing.html">Spring Testing</a> such 
as&#160;<code>@MockEndpoints</code>.</li><li>To turn on logging exhausted 
message body with the message history you can configure this easily on the 
CamelContext level with&#160;<code>setLogExhaustedMessageBody</code></li><li><a 
shape="rect" href="infinispan.html">Camel-Infinispan</a> now supports 
Aggregation Repository: InfinispanLocalAggregationRepository and 
InfinispanRemoteAggregationRepository</li><li>The&#160;<a shape="rect" 
href="sql-component.html">SQL Component</a>&#160;and <a shape="rect" 
href="elsql.html">ElSql</a>&#160;now supports 
<code>outputType=StreamList</code>&#16
 0;to use an iterator for the output of the SQL query that allows to process 
the data in a streaming fashion such as with the&#160;<a shape="rect" 
href="splitter.html">Splitter</a> EIP to process the data row by row, and load 
data from the database as needed.</li><li><a shape="rect" 
href="jpa.html">JPA</a> now includes a&#160;<code>JpaPollingConsumer</code> 
implementation that better supports&#160;<a shape="rect" 
href="content-enricher.html">Content Enricher</a> 
using&#160;<code>pollEnrich</code> to do a on-demand poll that returns either 
none, one or a list of entities as the result.&#160;</li><li>Calling&#160;<a 
shape="rect" href="bean.html">Bean</a>&#160;with method parameters defined 
using&#160;<a shape="rect" href="simple.html">Simple</a> parameters, now avoids 
an intermediate conversion of the parameters to a String value. This ensures 
the passed in values when calling the bean method is using the parameter type 
as-is from&#160;<a shape="rect" href="simple.html">Simple</a>.</li
 ><li><a shape="rect" href="cdi.html">Camel CDI</a> now supports importing 
 >Camel XML configuration files</li><li><a shape="rect" href="cdi.html">Camel 
 >CDI</a>&#160;does not deploy an empty Camel context bean anymore if not route 
 >builder beans nor Camel beans are deployed</li><li><a shape="rect" 
 >href="cdi.html">Camel CDI</a>&#160;adds the&#160;<code>@Named</code> 
 >qualifier to Camel route management events so that it's possible to observe 
 >these events for a specific route with an explicit <code>id</code></li><li><a 
 >shape="rect" href="beanio.html">Camel BeanIO</a> now supports the possibility 
 >to use a custom BeanReaderErrorHandler implementation in his 
 >configuration</li><li><a shape="rect" href="kubernetes.html">Camel 
 >Kubernetes</a> now supports Kubernetes ConfigMap feature</li><li>The&#160;<a 
 >shape="rect" href="tokenizer.html">Tokenizer</a> and&#160;<a shape="rect" 
 >href="xmltokenizer.html">XMLTokenizer</a> language now supports using <a 
 >shape="rect" href="simple.html">Simple</a> expres
 sions as the token / xml tag names so they can be dynamic 
values.</li><li>Added&#160;<code>filterDirectory</code> 
and&#160;<code>filterFile</code> options to&#160;<a shape="rect" 
href="file2.html">File2</a> so filtering can be done using&#160;<a shape="rect" 
href="simple.html">Simple</a> language or predicates.&#160;</li><li>Optimize 
Camel to only enable AllowUseOriginalMessage if in use by error handler 
or&#160;<a shape="rect" href="oncompletion.html">OnCompletion</a>. End user who 
manually access the original message using the Java API must 
configure&#160;AllowUseOriginalMessage=true.</li><li><a shape="rect" 
href="ahc.html">Camel-AHC</a> <a shape="rect" 
href="http.html">Camel-HTTP</a>&#160;<a shape="rect" 
href="http4.html">Camel-HTTP4</a>&#160;<a shape="rect" 
href="jetty.html">Camel-Jetty</a>&#160;now support a connectionClose parameter 
to allow explicitly adding a Connection Close header to HTTP request</li><li><a 
shape="rect" href="bindy.html">Bindy</a>&#160;allows to plugin cus
 tom formatters for mapping to custom types.</li><li><a shape="rect" 
href="content-enricher.html">Content Enricher</a> 
using&#160;<code>pollEnrich</code> now supports consumers configured 
with&#160;<code>consumer.bridgeErrorHandler=true</code> to let any exceptions 
from the poll propagate to the route error handler, to let it be able to 
perform redeliveries and whatnot.</li><li><a shape="rect" 
href="cxf.html">CXF</a> and <a shape="rect" href="cxfrs.html">CXFRS</a> now 
support setting of the SSL-context <a shape="rect" 
href="camel-configuration-utilities.html">Using the JSSE Configuration 
Utility</a></li><li><a shape="rect" href="mongodb.html">MongoDB</a> now is 
fully converted to MongoDB 3 although we still use BasicDBObject instead of 
Document</li><li>Camel Spring Boot can now scan for classes in Spring Boot FAR 
jars with embeds third party JARs.</li><li>You can now set the SNI Hostnames 
using the <a shape="rect" href="camel-configuration-utilities.html">Camel 
Configuration Utilitie
 s</a> to indicate the hostnames you try to connect</li><li>The XML DSL will 
preserve double spaces in the context-path of uri attributes when removing 
white space noise, when uri's are configured using mutli lines.</li><li>The 
Camel Catalog module can now load older versions of Camel to be used when 
querying the catalog. There is 
a&#160;<code>camel-catalog-maven</code>&#160;module that is able to download 
catalog JARs from Maven central.</li><li><p>A new Camel Attachment interface 
was added that allows propagating headers for attachments. <a shape="rect" 
href="cxf.html">Camel CXF</a>, <a shape="rect" href="mail.html">Camel Mail</a> 
(including the <a shape="rect" href="mime-multipart.html">MIME-Multipart 
</a>data format), and <a shape="rect" href="jetty.html">Camel-Jetty</a> set and 
consume attachment headers.</p></li></ul><p>Fixed these 
issues:</p><ul><li>Fixed&#160;<a shape="rect" href="bean.html">Bean</a> 
component to avoid ambiguous error for classes that extends generic interfac
 e and calling which could lead to falsely duplicate methods (due Java type 
erasure inserts bridge methods)&#160;</li><li>Fixed splitting 
using&#160;tarfile could cause OOME if splitting big files which was mistakenly 
loaded into memory. Now we work on the tar stream 
directly.</li><li>Fixed&#160;<a shape="rect" href="netty-http.html">Netty 
HTTP</a> and&#160;<a shape="rect" href="netty4-http.html">Netty4 HTTP</a> issue 
when not specifying a port number then port 80 would not be used but an error 
about port -1 is not allowed.</li><li>Fixed&#160;<a shape="rect" 
href="swagger-java.html">Swagger Java</a> when using property placeholders 
in&#160;<a shape="rect" href="rest-dsl.html">Rest DSL</a> could cause invalid 
parameters to be included that was from the 
placeholder.</li><li>The&#160;<code>threads</code>&#160;EIP now lets&#160;<a 
shape="rect" href="error-handling-in-camel.html">Error handling in 
Camel</a>&#160;perform redeliveries if the thread pool would otherwise reject 
accepting the 
 task. This allows the error handler to perform redeliveries to attempt to put 
the task on the thread pool queue, or eventually move the message to a dead 
letter queue etc.</li><li>Fixed&#160;<a shape="rect" href="rest-dsl.html">Rest 
DSL</a> adding empty header if specifying a non required query parameter that 
has no default value assigned.</li><li>Fixed <a shape="rect" 
href="loop.html">doWhile</a> loop which could potentially loop 
forever.</li><li>Fixed a NPE in&#160;<a shape="rect" 
href="zookeeper.html">Zookeeper</a> consumer if no zookeeper node path was 
set</li><li>When using continued with <a shape="rect" 
href="exception-clause.html">onException</a> then dead letter channel endpooint 
should not be invoked.</li><li>Fixed&#160;<a shape="rect" 
href="error-handler.html">Error Handler</a> to not log exceptions when 
using&#160;<code>continued(true)</code> by default.</li><li>Fixed so using 
shareUnitOfWork would now also call 
specialized&#160;<code>AggregationStrategy</code>&#160;for o
 nTimeout, onCompletion etc.</li><li>Fixed&#160;<a shape="rect" 
href="jetty.html">Jetty</a> consumer incorrectly handle multipart/form data not 
being mapped as attachments on the Camel Message.</li><li>Fixed&#160;<a 
shape="rect" href="netty4-http.html">Netty4 HTTP</a> may fail reading the http 
content from the raw netty stream if the Exchange was routed 
asynchronously.</li><li>Fixed&#160;<a shape="rect" 
href="netty4-http.html">Netty4 HTTP</a> leak ByteBuf's on the producer side 
which was not released in all corner cases before they may be gargage 
collected.&#160;</li><li>Fixed&#160;<a shape="rect" href="dozer.html">Dozer</a> 
not able to use variables in mapping files when using OSGi.</li><li>Fixed a 
potential&#160;dead-lock when doing request/reply over&#160;<a shape="rect" 
href="jms.html">JMS</a> and requests are timing out concurrently and continued 
routing the exchanges are calling another <a shape="rect" 
href="jms.html">JMS</a> endpoint that is also doing request/reply which also
  timeout.&#160;</li><li>Fixed&#160;<a shape="rect" 
href="load-balancer.html">Load Balancer</a> EIPs to support 
using&#160;<em>any</em> <a shape="rect" 
href="using-propertyplaceholder.html">property placeholder</a> using the 
<strong>prop:</strong> prefix.</li><li>Fixed context scoped&#160;<a 
shape="rect" href="oncompletion.html">OnCompletion</a>&#160;would not 
stop/shutdown its processors when&#160;CamelContext is being 
shutdown.&#160;</li><li>Fixed memory leak in&#160;<a shape="rect" 
href="routing-slip.html">Routing Slip</a> when the slip routes to certain kind 
of Camel components.</li><li>Fixed&#160;<a shape="rect" 
href="sql-component.html">SQL Component</a> query parameter mis-match issue 
when using IN queries together with other named parameters.</li><li>Fixed a 
preformance regression when using&#160;<code>camel-jaxb</code></li></ul><h3 
id="Camel2.18.0Release-New">New <a shape="rect" 
href="enterprise-integration-patterns.html">Enterprise Integration 
Patterns</a></h3><h3 id="Camel
 2.18.0Release-New.1">New <a shape="rect" 
href="components.html">Components</a></h3><ul><li>camel-cm-sms - For sending 
SMS messages using SM SMS Gateway.</li><li><a shape="rect" 
href="consul-component.html">camel-consul</a>&#160;- For integrating your 
application with&#160;<a shape="rect" class="external-link" 
href="https://www.consul.io/"; rel="nofollow">Consul</a>.</li><li><a 
shape="rect" href="ehcache.html">camel-ehcache</a>&#160;- For interacting with 
Ehcache 3 cache.</li><li><a shape="rect" href="flink.html">camel-flink</a> - 
Bridges Camel connectors with Apache Flink tasks.</li><li><a shape="rect" 
href="lumberjack.html">camel-lumberjack</a> - For receiving logs over the 
lumberjack protocol (used by Filebeat for instance)</li><li>camel-ribbon - To 
use Netflixx Ribbon with the&#160;<a shape="rect" 
href="servicecall-eip.html">Service Call EIP</a>.</li><li>camel-servicenow - 
For cloud management with ServiceNow.</li><li>camel-telegram - For messaging 
with Telegram.</li><li><a shape=
 "rect" href="camel-zipkin.html">camel-zipkin</a> - For tracking Camel message 
flows/timings using <a shape="rect" class="external-link" 
href="http://zipkin.io/"; style="line-height: 1.42857;" 
rel="nofollow">zipkin</a>.</li></ul><h3 id="Camel2.18.0Release-NewDSL">New 
DSL</h3><ul><li><a shape="rect" href="hystrix-eip.html">hystrix</a> - Using 
Netflixx Hystrix as circuit breaker. This requires 
having&#160;<code>camel-hsytrix</code> on the classpath.</li><li><a 
shape="rect" href="servicecall-eip.html">serviceCall</a> -&#160;To call a 
remote service in a distributed system where the service is looked up from a 
service registry of some sorts.</li></ul><h3 
id="Camel2.18.0Release-NewAnnotations">New Annotations</h3><h3 
id="Camel2.18.0Release-NewDataFormats">New <a shape="rect" 
href="data-format.html">Data Formats</a></h3><h3 
id="Camel2.18.0Release-New.2">New <a shape="rect" 
href="languages.html">Languages</a></h3><h3 id="Camel2.18.0Release-New.3">New 
<a shape="rect" href="examples.html">Exam
 ples</a></h3><ul><li><code>camel-example-cdi-xml</code>: i<span style="color: 
rgb(0,0,0);">llustrates the use of Camel XML configuration files into a Camel 
CDI application</span></li></ul><h3 id="Camel2.18.0Release-New.4">New <a 
shape="rect" href="tutorials.html">Tutorials</a></h3><h2 
id="Camel2.18.0Release-APIbreaking">API breaking</h2><ul><li>Removed the 
deprecated vtdxml language. You can use the generic language("vtdxml") 
instead</li></ul><h2 id="Camel2.18.0Release-KnownIssues">Known Issues</h2><h2 
id="Camel2.18.0Release-Importantchangestoconsiderwhenupgrading">Important 
changes to consider when upgrading</h2><ul><li><strong>Java 1.8 is now 
required.</strong></li><li>Karaf 2.4.x is no longer supported. Karaf 4.x is the 
primary supported OSGi platform.</li><li>Jetty 8.x is no longer supported and 
camel-jetty8 has been removed</li><li>spring 4.0 is no longer supported 
and&#160;camel-test-spring40 has been removed</li><li>spring 3.x is no longer 
supported</li><li>(only spring-dm us
 ing spring 3.2.x as part of camel-spring in osgi/karaf is still in use - but 
spring-dm is deprecated and we recommend using blueprint)</li><li>Spring-DM for 
OSGi moved out of camel-spring into a separate camel-spring-dm module. If using 
Spring XML with Spring-DM then you need to install camel-spring-dm feature in 
Karaf/ServiceMix.</li><li>The deprecated <code>@LazyLoadTypeConverter</code> 
has been removed from all&#160;<a shape="rect" href="camel-test.html">Camel 
Test</a> modules</li><li>camel-gae has been removed (was not working 
anyway)</li><li>The access in the&#160;<a shape="rect" 
href="rest-dsl.html">Rest DSL</a> has been deprecated and no longer in use - 
its not part of swagger specification anymore.</li><li>Removed the deprecated 
maven archetypes for SOAP WS using CXF with OSGi Blueprint</li><li>The XML DSL 
will preserve double spaces in the context-path of uri attributes when removing 
white space noise, when uri's are configured using mutli 
lines.</li><li>Optimize Camel to o
 nly enable AllowUseOriginalMessage if in use by error handler or&#160;<a 
shape="rect" href="oncompletion.html">OnCompletion</a>. End user who manually 
access the original message using the Java API must 
configure&#160;AllowUseOriginalMessage=true.</li><li>The&#160;<a shape="rect" 
href="ftp2.html">FTPS</a>&#160;component is now using known hosts file from the 
user.home/.ssh directory by default. Set the 
option&#160;useUserKnownHostsFile=false to use old behavior.</li><li>the <a 
shape="rect" href="mongodb.html">MongoDB</a> component is migrated to MongoDB 
3. Returned objects might be different e.g. findAll always returns an Iterable 
(FindIterable or ArrayList). Sometimes the returning of headers is remove e.g. 
for the paged findAll the total size isn't fetch</li><li>the <a shape="rect" 
href="salesforce.html">Salesforce</a> component doesn't use jodatime anymore. 
It uses the java 8 ZonedDateTime. DTO's need to be changed or 
regenerated.</li></ul><h2 id="Camel2.18.0Release-GettingtheDis
 tributions">Getting the Distributions</h2><h3 
id="Camel2.18.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="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.18.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 for Windows</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.apac
 
he.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><div
 class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</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.tar.gz";>apache-camel-x.y.x-src.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-src.tar.gz.asc";>apache-camel-x.y.x-src.tar.gz.asc</a></p></td></tr></tbody></table></div><h3
 id="Camel2.18.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">
+<div class="wiki-content maincontent"><h1 
id="Camel2.18.0Release-Camel2.18.0release(currentlyinprogress)">Camel 2.18.0 
release (currently in progress)</h1><div 
style="padding-right:20px;float:left;margin-left:-20px;"><p><span 
class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image 
confluence-external-resource" 
src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png"; 
data-image-src="http://camel.apache.org/download.data/camel-box-v1.0-150x200.png";></span></p></div><div
 style="min-height:200px">&#160;</div><h2 
id="Camel2.18.0Release-NewandNoteworthy">New and Noteworthy</h2><p>Welcome to 
the 2.18.0 release which approx XXX issues resolved (new features, improvements 
and bug fixes such as...)</p><ul><li>All Camel&#160;<a shape="rect" 
href="components.html">Components</a> that has options to be configured now 
supports and include&#160;<a shape="rect" href="spring-boot.html">Spring 
Boot</a>&#160;auto configuration for those options, so they can easily 
 be configured in your application.yaml file when using Spring Boot with 
Camel.&#160;</li><li>Camel <a shape="rect" href="spring-boot.html">Spring 
Boot</a> now supports the same&#160;<a shape="rect" 
href="advanced-configuration-of-camelcontext-using-spring.html">advanced 
configuration</a>&#160;you can do with Spring XML, if the beans&#160;have been 
configured using&#160;<code>@Bean</code>&#160;style in a Spring Boot 
configuration class.</li><li>Added <a shape="rect" 
href="hystrix-eip.html">Hystrix EIP</a> as EIP pattern that uses native 
Netflixx Hystrix as the Circuit Breaker implementation.&#160;This requires 
having&#160;<code>camel-hystrix</code>&#160;on the 
classpath.</li><li>Added&#160;<a shape="rect" 
href="servicecall-eip.html">Service Call EIP</a> as EIP pattern that allows to 
call a remote service in a distributed system, where the service is looked up 
from a service registry of some sorts, such as kubernetes, consul, etcd, 
zookeeper etc.</li><li><span style="line-height: 1.42
 857;">Running Camel with&#160;<a shape="rect" href="spring-boot.html">Spring 
Boot</a> now includes a Camel Health Indicator (actuator) if 
<code>spring-boot-starter-actuator</code>&#160;is on the 
classpath.</span></li><li>Spring-DM for OSGi moved out of camel-spring into a 
separate camel-spring-dm module.<span style="line-height: 1.42857;"><br 
clear="none"></span></li><li><span style="line-height: 1.42857;">Improved 
the&#160;</span><a shape="rect" href="bean.html">Bean</a><span 
style="line-height: 1.42857;"> component to better match method parameter types 
when using&#160;</span><a shape="rect" href="simple.html">Simple</a><span 
style="line-height: 1.42857;"> language as parameter 
values.</span></li><li>Added&#160;<code>BindyConverter</code> that allows to 
implement custom data converters for&#160;<a shape="rect" 
href="bindy.html">Bindy</a></li><li>The access in the&#160;<a shape="rect" 
href="rest-dsl.html">Rest DSL</a> has been deprecated and no longer in use - 
its not part of swagg
 er specification anymore.</li><li><a shape="rect" 
href="nats.html">Camel-NATS</a>&#160;now uses JNATS client instead of the 
deprecated Java_nats one.</li><li>During startup of&#160;<a shape="rect" 
href="camelcontext.html">CamelContext</a> the services that are used as part of 
routes are now deferred being started to the end of the startup process. Some 
IoC frameworks like Spring can otherwise causes a circular dependency issue if 
services are started too early. A side effect is that if service startup 
failures happen when being started later, they are now wrapped in the 
<code>FailedToStartupRouteException</code> to better pin point which route thas 
the problem.</li><li>Improved the startup sequence of&#160;<a shape="rect" 
href="spring-java-config.html">Spring Java Config</a> to be similar to&#160;<a 
shape="rect" href="spring-boot.html">Spring Boot</a> that helps prevent Spring 
initialization errors about circular dependencies issues.</li><li>Added PATCH 
to&#160;<a shape="rect" href=
 "rest-dsl.html">Rest DSL</a></li><li>Added "starts with" and "ends with" 
operator to the <a shape="rect" 
href="simple.html">Simple</a>&#160;language.</li><li>Added&#160;<code>BeanIOSplitter</code>
 to&#160;<a shape="rect" href="beanio.html">BeanIO</a> that can be used with 
the&#160;<a shape="rect" href="splitter.html">Splitter</a> EIP to split big 
payloads in streaming mode without reading the entire content into 
memory.</li><li>Some of the <a shape="rect" 
href="aws.html">AWS</a>&#160;components allows to specify ARN in the endpoint 
configuration.&#160;</li><li>The create operation in&#160;<a shape="rect" 
href="zookeeper.html">Zookeeper</a> now creates sub paths if 
missing.</li><li>Added support for async mode for&#160;<a shape="rect" 
href="servlet.html">SERVLET</a> component to leverage Asynchronous Servlet from 
the Servlet 3.0 spec.</li><li><a shape="rect" 
href="bean.html">Bean</a>&#160;component and <a shape="rect" 
href="bean-language.html">Bean Language</a>&#160;validates method 
 name must be a valid according to java identifier rules, and also if parameter 
syntax has an ending parenthesis.</li><li>You can now 
use&#160;<code>@RunWith(CamelSpringBootJUnit4ClassRunner.class)</code> to test 
Camel&#160;<a shape="rect" href="spring-boot.html">Spring 
Boot</a>&#160;applications and use the Camel test annotations from&#160;<a 
shape="rect" href="spring-testing.html">Spring Testing</a> such 
as&#160;<code>@MockEndpoints</code>.</li><li>To turn on logging exhausted 
message body with the message history you can configure this easily on the 
CamelContext level with&#160;<code>setLogExhaustedMessageBody</code></li><li><a 
shape="rect" href="infinispan.html">Camel-Infinispan</a> now supports 
Aggregation Repository: InfinispanLocalAggregationRepository and 
InfinispanRemoteAggregationRepository</li><li>The&#160;<a shape="rect" 
href="sql-component.html">SQL Component</a>&#160;and <a shape="rect" 
href="elsql.html">ElSql</a>&#160;now supports 
<code>outputType=StreamList</code>&#16
 0;to use an iterator for the output of the SQL query that allows to process 
the data in a streaming fashion such as with the&#160;<a shape="rect" 
href="splitter.html">Splitter</a> EIP to process the data row by row, and load 
data from the database as needed.</li><li><a shape="rect" 
href="jpa.html">JPA</a> now includes a&#160;<code>JpaPollingConsumer</code> 
implementation that better supports&#160;<a shape="rect" 
href="content-enricher.html">Content Enricher</a> 
using&#160;<code>pollEnrich</code> to do a on-demand poll that returns either 
none, one or a list of entities as the result.&#160;</li><li>Calling&#160;<a 
shape="rect" href="bean.html">Bean</a>&#160;with method parameters defined 
using&#160;<a shape="rect" href="simple.html">Simple</a> parameters, now avoids 
an intermediate conversion of the parameters to a String value. This ensures 
the passed in values when calling the bean method is using the parameter type 
as-is from&#160;<a shape="rect" href="simple.html">Simple</a>.</li
 ><li><a shape="rect" href="cdi.html">Camel CDI</a> now supports importing 
 >Camel XML configuration files</li><li><a shape="rect" href="cdi.html">Camel 
 >CDI</a>&#160;does not deploy an empty Camel context bean anymore if not route 
 >builder beans nor Camel beans are deployed</li><li><a shape="rect" 
 >href="cdi.html">Camel CDI</a>&#160;adds the&#160;<code>@Named</code> 
 >qualifier to Camel route management events so that it's possible to observe 
 >these events for a specific route with an explicit <code>id</code></li><li><a 
 >shape="rect" href="beanio.html">Camel BeanIO</a> now supports the possibility 
 >to use a custom BeanReaderErrorHandler implementation in his 
 >configuration</li><li><a shape="rect" href="kubernetes.html">Camel 
 >Kubernetes</a> now supports Kubernetes ConfigMap feature</li><li>The&#160;<a 
 >shape="rect" href="tokenizer.html">Tokenizer</a> and&#160;<a shape="rect" 
 >href="xmltokenizer.html">XMLTokenizer</a> language now supports using <a 
 >shape="rect" href="simple.html">Simple</a> expres
 sions as the token / xml tag names so they can be dynamic 
values.</li><li>Added&#160;<code>filterDirectory</code> 
and&#160;<code>filterFile</code> options to&#160;<a shape="rect" 
href="file2.html">File2</a> so filtering can be done using&#160;<a shape="rect" 
href="simple.html">Simple</a> language or predicates.&#160;</li><li>Optimize 
Camel to only enable AllowUseOriginalMessage if in use by error handler 
or&#160;<a shape="rect" href="oncompletion.html">OnCompletion</a>. End user who 
manually access the original message using the Java API must 
configure&#160;AllowUseOriginalMessage=true.</li><li><a shape="rect" 
href="ahc.html">Camel-AHC</a> <a shape="rect" 
href="http.html">Camel-HTTP</a>&#160;<a shape="rect" 
href="http4.html">Camel-HTTP4</a>&#160;<a shape="rect" 
href="jetty.html">Camel-Jetty</a>&#160;now support a connectionClose parameter 
to allow explicitly adding a Connection Close header to HTTP request</li><li><a 
shape="rect" href="bindy.html">Bindy</a>&#160;allows to plugin cus
 tom formatters for mapping to custom types.</li><li><a shape="rect" 
href="content-enricher.html">Content Enricher</a> 
using&#160;<code>pollEnrich</code> now supports consumers configured 
with&#160;<code>consumer.bridgeErrorHandler=true</code> to let any exceptions 
from the poll propagate to the route error handler, to let it be able to 
perform redeliveries and whatnot.</li><li><a shape="rect" 
href="cxf.html">CXF</a> and <a shape="rect" href="cxfrs.html">CXFRS</a> now 
support setting of the SSL-context <a shape="rect" 
href="camel-configuration-utilities.html">Using the JSSE Configuration 
Utility</a></li><li><a shape="rect" href="mongodb.html">MongoDB</a> now is 
fully converted to MongoDB 3 although we still use BasicDBObject instead of 
Document</li><li>Camel Spring Boot can now scan for classes in Spring Boot FAR 
jars with embeds third party JARs.</li><li>You can now set the SNI Hostnames 
using the <a shape="rect" href="camel-configuration-utilities.html">Camel 
Configuration Utilitie
 s</a> to indicate the hostnames you try to connect</li><li>The XML DSL will 
preserve double spaces in the context-path of uri attributes when removing 
white space noise, when uri's are configured using mutli lines.</li><li>The 
Camel Catalog module can now load older versions of Camel to be used when 
querying the catalog. There is 
a&#160;<code>camel-catalog-maven</code>&#160;module that is able to download 
catalog JARs from Maven central.</li><li><p>A new Camel Attachment interface 
was added that allows propagating headers for attachments. <a shape="rect" 
href="cxf.html">Camel CXF</a>, <a shape="rect" href="mail.html">Camel Mail</a> 
(including the <a shape="rect" href="mime-multipart.html">MIME-Multipart 
</a>data format), and <a shape="rect" href="jetty.html">Camel-Jetty</a> set and 
consume attachment headers.</p></li><li>Improved <a shape="rect" 
href="bean.html">bean method call</a> to validate if method name with 
parameters has valid number of parenthesis in the syntax.</li></ul><p
 >Fixed these issues:</p><ul><li>Fixed&#160;<a shape="rect" 
 >href="bean.html">Bean</a> component to avoid ambiguous error for classes that 
 >extends generic interface and calling which could lead to falsely duplicate 
 >methods (due Java type erasure inserts bridge methods)&#160;</li><li>Fixed 
 >splitting using&#160;tarfile could cause OOME if splitting big files which 
 >was mistakenly loaded into memory. Now we work on the tar stream 
 >directly.</li><li>Fixed&#160;<a shape="rect" href="netty-http.html">Netty 
 >HTTP</a> and&#160;<a shape="rect" href="netty4-http.html">Netty4 HTTP</a> 
 >issue when not specifying a port number then port 80 would not be used but an 
 >error about port -1 is not allowed.</li><li>Fixed&#160;<a shape="rect" 
 >href="swagger-java.html">Swagger Java</a> when using property placeholders 
 >in&#160;<a shape="rect" href="rest-dsl.html">Rest DSL</a> could cause invalid 
 >parameters to be included that was from the 
 >placeholder.</li><li>The&#160;<code>threads</code>&#160;EIP now lets&#160;<
 a shape="rect" href="error-handling-in-camel.html">Error handling in 
Camel</a>&#160;perform redeliveries if the thread pool would otherwise reject 
accepting the task. This allows the error handler to perform redeliveries to 
attempt to put the task on the thread pool queue, or eventually move the 
message to a dead letter queue etc.</li><li>Fixed&#160;<a shape="rect" 
href="rest-dsl.html">Rest DSL</a> adding empty header if specifying a non 
required query parameter that has no default value assigned.</li><li>Fixed <a 
shape="rect" href="loop.html">doWhile</a> loop which could potentially loop 
forever.</li><li>Fixed a NPE in&#160;<a shape="rect" 
href="zookeeper.html">Zookeeper</a> consumer if no zookeeper node path was 
set</li><li>When using continued with <a shape="rect" 
href="exception-clause.html">onException</a> then dead letter channel endpooint 
should not be invoked.</li><li>Fixed&#160;<a shape="rect" 
href="error-handler.html">Error Handler</a> to not log exceptions when 
using&#160
 ;<code>continued(true)</code> by default.</li><li>Fixed so using 
shareUnitOfWork would now also call 
specialized&#160;<code>AggregationStrategy</code>&#160;for onTimeout, 
onCompletion etc.</li><li>Fixed&#160;<a shape="rect" 
href="jetty.html">Jetty</a> consumer incorrectly handle multipart/form data not 
being mapped as attachments on the Camel Message.</li><li>Fixed&#160;<a 
shape="rect" href="netty4-http.html">Netty4 HTTP</a> may fail reading the http 
content from the raw netty stream if the Exchange was routed 
asynchronously.</li><li>Fixed&#160;<a shape="rect" 
href="netty4-http.html">Netty4 HTTP</a> leak ByteBuf's on the producer side 
which was not released in all corner cases before they may be gargage 
collected.&#160;</li><li>Fixed&#160;<a shape="rect" href="dozer.html">Dozer</a> 
not able to use variables in mapping files when using OSGi.</li><li>Fixed a 
potential&#160;dead-lock when doing request/reply over&#160;<a shape="rect" 
href="jms.html">JMS</a> and requests are timing out 
 concurrently and continued routing the exchanges are calling another <a 
shape="rect" href="jms.html">JMS</a> endpoint that is also doing request/reply 
which also timeout.&#160;</li><li>Fixed&#160;<a shape="rect" 
href="load-balancer.html">Load Balancer</a> EIPs to support 
using&#160;<em>any</em> <a shape="rect" 
href="using-propertyplaceholder.html">property placeholder</a> using the 
<strong>prop:</strong> prefix.</li><li>Fixed context scoped&#160;<a 
shape="rect" href="oncompletion.html">OnCompletion</a>&#160;would not 
stop/shutdown its processors when&#160;CamelContext is being 
shutdown.&#160;</li><li>Fixed memory leak in&#160;<a shape="rect" 
href="routing-slip.html">Routing Slip</a> when the slip routes to certain kind 
of Camel components.</li><li>Fixed&#160;<a shape="rect" 
href="sql-component.html">SQL Component</a> query parameter mis-match issue 
when using IN queries together with other named parameters.</li><li>Fixed a 
preformance regression when using&#160;<code>camel-jaxb</cod
 e></li></ul><h3 id="Camel2.18.0Release-New">New <a shape="rect" 
href="enterprise-integration-patterns.html">Enterprise Integration 
Patterns</a></h3><h3 id="Camel2.18.0Release-New.1">New <a shape="rect" 
href="components.html">Components</a></h3><ul><li>camel-cm-sms - For sending 
SMS messages using SM SMS Gateway.</li><li><a shape="rect" 
href="consul-component.html">camel-consul</a>&#160;- For integrating your 
application with&#160;<a shape="rect" class="external-link" 
href="https://www.consul.io/"; rel="nofollow">Consul</a>.</li><li><a 
shape="rect" href="ehcache.html">camel-ehcache</a>&#160;- For interacting with 
Ehcache 3 cache.</li><li><a shape="rect" href="flink.html">camel-flink</a> - 
Bridges Camel connectors with Apache Flink tasks.</li><li><a shape="rect" 
href="lumberjack.html">camel-lumberjack</a> - For receiving logs over the 
lumberjack protocol (used by Filebeat for instance)</li><li>camel-ribbon - To 
use Netflixx Ribbon with the&#160;<a shape="rect" href="servicecall-eip.htm
 l">Service Call EIP</a>.</li><li>camel-servicenow - For cloud management with 
ServiceNow.</li><li>camel-telegram - For messaging with Telegram.</li><li><a 
shape="rect" href="camel-zipkin.html">camel-zipkin</a> - For tracking Camel 
message flows/timings using <a shape="rect" class="external-link" 
href="http://zipkin.io/"; style="line-height: 1.42857;" 
rel="nofollow">zipkin</a>.</li></ul><h3 id="Camel2.18.0Release-NewDSL">New 
DSL</h3><ul><li><a shape="rect" href="hystrix-eip.html">hystrix</a> - Using 
Netflixx Hystrix as circuit breaker. This requires 
having&#160;<code>camel-hsytrix</code> on the classpath.</li><li><a 
shape="rect" href="servicecall-eip.html">serviceCall</a> -&#160;To call a 
remote service in a distributed system where the service is looked up from a 
service registry of some sorts.</li></ul><h3 
id="Camel2.18.0Release-NewAnnotations">New Annotations</h3><h3 
id="Camel2.18.0Release-NewDataFormats">New <a shape="rect" 
href="data-format.html">Data Formats</a></h3><h3 id="Came
 l2.18.0Release-New.2">New <a shape="rect" 
href="languages.html">Languages</a></h3><h3 id="Camel2.18.0Release-New.3">New 
<a shape="rect" 
href="examples.html">Examples</a></h3><ul><li><code>camel-example-cdi-xml</code>:
 i<span style="color: rgb(0,0,0);">llustrates the use of Camel XML 
configuration files into a Camel CDI application</span></li></ul><h3 
id="Camel2.18.0Release-New.4">New <a shape="rect" 
href="tutorials.html">Tutorials</a></h3><h2 
id="Camel2.18.0Release-APIbreaking">API breaking</h2><ul><li>Removed the 
deprecated vtdxml language. You can use the generic language("vtdxml") 
instead</li></ul><h2 id="Camel2.18.0Release-KnownIssues">Known Issues</h2><h2 
id="Camel2.18.0Release-Importantchangestoconsiderwhenupgrading">Important 
changes to consider when upgrading</h2><ul><li><strong>Java 1.8 is now 
required.</strong></li><li>Karaf 2.4.x is no longer supported. Karaf 4.x is the 
primary supported OSGi platform.</li><li>Jetty 8.x is no longer supported and 
camel-jetty8 has been rem
 oved</li><li>spring 4.0 is no longer supported and&#160;camel-test-spring40 
has been removed</li><li>spring 3.x is no longer supported</li><li>(only 
spring-dm using spring 3.2.x as part of camel-spring in osgi/karaf is still in 
use - but spring-dm is deprecated and we recommend using 
blueprint)</li><li>Spring-DM for OSGi moved out of camel-spring into a separate 
camel-spring-dm module. If using Spring XML with Spring-DM then you need to 
install camel-spring-dm feature in Karaf/ServiceMix.</li><li>The deprecated 
<code>@LazyLoadTypeConverter</code> has been removed from all&#160;<a 
shape="rect" href="camel-test.html">Camel Test</a> modules</li><li>camel-gae 
has been removed (was not working anyway)</li><li>The access in the&#160;<a 
shape="rect" href="rest-dsl.html">Rest DSL</a> has been deprecated and no 
longer in use - its not part of swagger specification anymore.</li><li>Removed 
the deprecated maven archetypes for SOAP WS using CXF with OSGi 
Blueprint</li><li>The XML DSL will prese
 rve double spaces in the context-path of uri attributes when removing white 
space noise, when uri's are configured using mutli lines.</li><li>Optimize 
Camel to only enable AllowUseOriginalMessage if in use by error handler 
or&#160;<a shape="rect" href="oncompletion.html">OnCompletion</a>. End user who 
manually access the original message using the Java API must 
configure&#160;AllowUseOriginalMessage=true.</li><li>The&#160;<a shape="rect" 
href="ftp2.html">FTPS</a>&#160;component is now using known hosts file from the 
user.home/.ssh directory by default. Set the 
option&#160;useUserKnownHostsFile=false to use old behavior.</li><li>the <a 
shape="rect" href="mongodb.html">MongoDB</a> component is migrated to MongoDB 
3. Returned objects might be different e.g. findAll always returns an Iterable 
(FindIterable or ArrayList). Sometimes the returning of headers is remove e.g. 
for the paged findAll the total size isn't fetch</li><li>the <a shape="rect" 
href="salesforce.html">Salesforce</a> com
 ponent doesn't use jodatime anymore. It uses the java 8 ZonedDateTime. DTO's 
need to be changed or regenerated.</li></ul><h2 
id="Camel2.18.0Release-GettingtheDistributions">Getting the 
Distributions</h2><h3 id="Camel2.18.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.apac
 
he.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 syst
 em 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.18.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 for Windows</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><div
 class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</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.tar.gz";>apache-camel-x.y.x-src.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-src.tar.gz.asc";>apache-camel-x.y.x-src.tar.gz.asc</a></p></td></tr></tbody></table></div><h3
 id="Camel2.18.0Release-GettingtheBinariesusingMaven
 2">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: xml; 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