[
https://issues.apache.org/jira/browse/CAMEL-22221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jannik Schmeier updated CAMEL-22221:
------------------------------------
Description:
I came across an issue with dependency incompatibilities when using Spring Boot
3.5.3 and Camel Spring Boot BOM 4.12.0.
When using Spring Boot Parent together with importing Camel Spring Boot BOM in
the dependencyManagement section, the micrometer version 1.15.1 of spring boot
is being overridden with 1.15.0 from Camel Spring Boot BOM and due to that
retrieving Prometheus metrics in protobuf format from the Actuator endpoint
breaks with a NoClassDefFoundError.
IMHO the Camel Spring Boot BOM shouldn't manage any other dependencies than the
Camel ones, but currently it also manages various other dependencies (protobuf,
grpc, micrometer, netbuddy, avro). As you can see this can cause unwanted
overrides of spring boot dependency versions and ultimately break functionality.
I have tried explicitly adding Spring Boot Dependencies BOM before Camel Spring
Boot BOM, but it has not fixed my issue. As a workaround, I will stop using
Camel Spring Boot BOM for now.
If you need, I can provide a sample maven project.
was:
I came across an issue with dependency incompatibilities when using Spring Boot
3.5.3 and Camel Spring Boot BOM 4.12.0.
When using Spring Boot Parent together with importing Camel Spring Boot BOM in
the dependencyManagement section, the micrometer version 1.15.1 of spring boot
is being overridden with 1.15.0 from Camel Spring Boot BOM and due to that
retrieving Prometheus metrics in protobuf format from the Actuator endpoint
breaks with a NoClassDefFoundError.
IMHO the Camel Spring Boot BOM shouldn't manage any other dependencies than the
Camel ones, but currently it also manages various other dependencies (protobuf,
grpc, micrometer, netbuddy, avro). As you can see this can cause unwanted
overrides of spring boot dependency versions and ultimately break functionality.
As a workaround, I will stop using Camel Spring Boot BOM for now.
If you need, I can provide a sample maven project.
EDIT: I just saw the documentation here: [Apache Camel Spring Boot starters ::
Apache Camel|https://camel.apache.org/camel-spring-boot/4.10.x/index.html]
And I explicitly defined the Spring Boot Dependencies BOM and BEFORE the Camel
one, now it works for me. Nevertheless, it might be beneficial to remove the
mentioned dependencies from the BOM.
> Camel Spring Boot BOM should only manage Camel dependencies
> -----------------------------------------------------------
>
> Key: CAMEL-22221
> URL: https://issues.apache.org/jira/browse/CAMEL-22221
> Project: Camel
> Issue Type: Improvement
> Affects Versions: 4.12.0
> Reporter: Jannik Schmeier
> Priority: Major
>
> I came across an issue with dependency incompatibilities when using Spring
> Boot 3.5.3 and Camel Spring Boot BOM 4.12.0.
>
> When using Spring Boot Parent together with importing Camel Spring Boot BOM
> in the dependencyManagement section, the micrometer version 1.15.1 of spring
> boot is being overridden with 1.15.0 from Camel Spring Boot BOM and due to
> that retrieving Prometheus metrics in protobuf format from the Actuator
> endpoint breaks with a NoClassDefFoundError.
>
> IMHO the Camel Spring Boot BOM shouldn't manage any other dependencies than
> the Camel ones, but currently it also manages various other dependencies
> (protobuf, grpc, micrometer, netbuddy, avro). As you can see this can cause
> unwanted overrides of spring boot dependency versions and ultimately break
> functionality.
>
> I have tried explicitly adding Spring Boot Dependencies BOM before Camel
> Spring Boot BOM, but it has not fixed my issue. As a workaround, I will stop
> using Camel Spring Boot BOM for now.
> If you need, I can provide a sample maven project.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
