Another related issue is that the Spring initializer https://start.spring.io/ ,
can generate a project including Camel (after the resolution of
https://github.com/spring-io/initializr/issues/207), but
camel-spring-boot-starter version in the dependencies is not managed by
spring-boot-starter-parent.
So one big advantage that spring boot offers - to manage the dependencies
version - is getting lost if you add some starters like camel.
No matter which version of Spring Boot you select(1.2.8 ->1.4.0.M2) you get
Camel 2.17.0.
I believe this is somehow fragile and probably will raise more dependency
conflicts.
On Friday, April 22, 2016 2:11 PM, Lefteris Tsallas <ltsal...@yahoo.com>
wrote:
I see.
According to their current documentation "The client must have the same major
version (e.g. 2.x, or 5.x) as thenodes in the cluster" .
This does not look like a major limitation.
On Friday, April 22, 2016 1:57 PM, Claus Ibsen <claus.ib...@gmail.com>
wrote:
And I hear that the ES guys are working on a Java client that is more
agnostic what ES server version you use. The current Java client is
too tightly coupled to the server version.
On Fri, Apr 22, 2016 at 11:12 AM, Claus Ibsen <claus.ib...@gmail.com> wrote:
> This is not a Camel problem.
>
> Its limitation with spring boot if they only work with old ES version.
>
> On Fri, Apr 22, 2016 at 11:04 AM, Lefteris Tsallas
> <ltsal...@yahoo.com.invalid> wrote:
>> Hi all,
>>
>> I started a new Camel Spring Boot project using the maven archetype
>> camel-archetype-spring-boot. Camel Version 2.17.0 gets Spring Boot 1.3.3
>> After adding the camel-elasticsearch component, it requests
>>org.elasticsearch:elasticsearch:2.2.0 but Spring boot 1.3.3 forces
>>elasticsearch1.5.2 to be picked.
>>
>> So If you add a route with elasticsearch component the application fails to
>> start and you you get
>> java.lang.NoSuchMethodError:
>> org.elasticsearch.node.NodeBuilder.getSettings()Lorg/elasticsearch/common/settings/Settings$Builder;
>>
>>
>>
>> I can resolve this by adding elasticsearch 2.2.0 as a top level dependency
>>in my project. Can you suggest a better approach? Should I open a JIRA for
>>that?
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
