[
https://issues.apache.org/jira/browse/CAMEL-11756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161199#comment-16161199
]
Nicola Ferraro commented on CAMEL-11756:
----------------------------------------
Yes, it can be achieved. The only problem I foresee is when spring-boot2 will
get updated with newer version of dependent libs (think about Jetty), while the
1.5.x branch will not be updated. This will force us to make our components
work with different *major* versions of some libraries and sometimes this is
really hard to achieve.
So, it's possible that we will decide to drop support for spring-boot 1.x
before 3.x, but let's open both possibilities for now.
I can fix these generated dependencies on camel-spring-boot if you are not
working on it.
> camel-spring-boot2 - Create experimental spring boot 2 component
> ----------------------------------------------------------------
>
> Key: CAMEL-11756
> URL: https://issues.apache.org/jira/browse/CAMEL-11756
> Project: Camel
> Issue Type: Task
> Components: camel-spring-boot
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.20.0
>
>
> We should try get started with the migration effort for getting Camel running
> on Spring Boot 2.0.x.
> There may be issues with the starter component as Spring Boot guys changed
> stuff how auto configuration and setting properties works. So we may need to
> have some kind of interface in camel-spring-boot and camel-spring-boot2 where
> we can have different implementation that the -starter can use.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
