[ 
https://issues.apache.org/jira/browse/CAMEL-27273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18148039#comment-18148039
 ] 

James Netherton commented on CAMEL-27273:
-----------------------------------------

Yes, it should be fine. We've been out of alignment with kafka-clients compared 
to Quarkus for a long time and I don't ever recall seeing issues related to it.

> Align Kafka, log4j2 and Hazelcast with the versions of Spring Boot 4.2
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-27273
>                 URL: https://issues.apache.org/jira/browse/CAMEL-27273
>             Project: Camel
>          Issue Type: Dependency upgrade
>          Components: camel-hazelcast, camel-kafka, camel-spring-boot
>            Reporter: Federico Mariani
>            Priority: Major
>
> Spring Boot 4.2.0 (CAMEL-26590) manages newer versions than Camel for:
> ||Library||Camel ({{parent/pom.xml}})||Spring Boot 4.2.0||
> |Kafka ({{kafka-clients}})|4.3.2|4.4.0|
> |log4j2|2.25.5|2.26.1|
> |Hazelcast|5.4.0|5.7.0|
> Applications that use the Spring Boot dependency management (starter parent 
> or BOM) get the Boot versions, so camel-kafka and camel-hazelcast run there 
> with newer clients than the ones Camel builds and tests with (log4j2 too, 
> with {{spring-boot-starter-log4j2}}).
> Proposal: upgrade the three in Camel to the Spring Boot 4.2 versions. 
> Hazelcast stays on 5.4.0 on purpose because of CAMEL-22041 (the tests use the 
> CP subsystem, commercial since 5.5), so it needs that one first.
> [~davsclaus] [~jamesnetherton] is this OK from the Camel and Camel Quarkus 
> point of view?
> _Claude Code on behalf of Federico Mariani_



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to