[
https://issues.apache.org/jira/browse/CAMEL-11756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164310#comment-16164310
]
Nicola Ferraro commented on CAMEL-11756:
----------------------------------------
Here's the list of modules that for some reasons import "commons-configuration"
and may incur in the same problem:
{code}
camel-flink
camel-gora
camel-hbase
camel-hdfs
camel-hdfs2
camel-hystrix
camel-ribbon
camel-spark
{code}
[~snicoll] I was thinking to open a issue in spring to include something from
the "impl" package because, despite its name, that package is actually used by
third party libraries, usually just for the NoOpLog. This way the transition
will be smoother. If we just add commons-logging as transitive dependency there
will be classloading clashes. Wdyt?
> 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)
