Repository navigation
chore: align example dependency versions with Camel and Spring Boot - #223
Merged
Merged
Conversation
Align the dependency and plugin versions declared by the examples with the ones managed by Camel (camel-dependencies), camel-spring-boot and the Spring Boot 4.1.2 BOM, and bump to the latest release where neither defines a version. - Drop module/root properties that shadowed newer Camel versions (reactor, testcontainers, log4j2, spring-ai, langchain4j) and unused ones (activemq-version, kafka-avro-serializer-version, jolokia). - observation/loggingtracer: use the examples parent and the Spring Boot BOM instead of pinning micrometer-core 1.13.15 / brave 6.0.3 (fixes the micrometer-core security alert). - Use Camel properties for postgresql, build-helper-maven-plugin, agroal and hapi. - Artemis: org.apache.activemq -> org.apache.artemis (relocated groupId), version managed by Spring Boot. - Bump JKube, Strimzi kafka-oauth (property renamed to strimzi-kafka-oauth-version), narayana-spring-boot-starter, swagger-codegen-maven-plugin and the OpenTelemetry java agent (one shared opentelemetry-javaagent-version property). - Pin unversioned spring-boot-maven-plugin, build-helper-maven-plugin, openshift-maven-plugin and native-maven-plugin. - resilience4j client2/service2: log4j-slf4j-impl -> log4j-slf4j2-impl (SLF4J 2.x). - openapi-contract-first: validationMode=legacy keeps the generated models unchanged with swagger-codegen 3.0.85.
davsclaus
approved these changes
Nov 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Aligns the dependency and plugin versions declared by the examples with the ones managed by Camel (
camel-dependencies), camel-spring-boot and the Spring Boot 4.1.2 BOM. Where none of them defines a version, the dependency is bumped to its latest release.This also resolves the Dependabot alert for
io.micrometer:micrometer-core(>= 1.10.0, <= 1.13.15), which was pinned to 1.13.15 inobservation/loggingtracer.Overrides that shadowed newer Camel / Spring Boot versions (removed)
reactor-version(reactive-streams)testcontainers-version(azure-storage-blob, multi-datasource-2pc)resilience4jlog4j2-versionai-agentspring-ai-versiongenai-observabilitylangchain4j starter1.20.0+ hardcoded-beta30${langchain4j-beta-version}1.23.0-beta33observation/loggingtracermicrometer-core / bravemicrometer-tracing.version) / 6.0.3observation/loggingtracerhad no<parent>, so it could not inherit any managed version (it was also compiled at the compiler plugin's default level instead of Java 21). It now uses the examples root as parent and imports the Spring Boot BOM. It does not usecamel-example-spring-boot-observationas parent, because that would apply Spring Boot repackaging to a plain library.Also removed the unused
activemq-version(activemq) andkafka-avro-serializer-version(root) properties.Hardcoded versions replaced with the Camel property
org.postgresql:postgresql42.7.12 ->${pgjdbc-driver-version}(42.7.14)build-helper-maven-plugin3.0.0 / 3.5.0 / unversioned ->${build-helper-maven-plugin-version}(3.7.0)agroal-spring-boot-starter3.0 ->${agroal-version}(3.2.1)hapi-structures-v24->${hapi-version}(unchanged 2.6.0, drops the duplicate root property)Artemis groupId relocation
artemisandsagausedorg.apache.activemq:artemis-jakarta-*, which has been relocated toorg.apache.artemis. Theartemisexample pinned 2.44.0, so the classpath mixed 2.44.0 jars with the 2.53.0 jars managed by Spring Boot. Both examples now useorg.apache.artemis, with the version managed by the Spring Boot BOM.Not managed by Camel / Spring Boot: bumped to latest
kubernetes-maven-plugin1.19.0 -> 1.20.0.openshift-maven-plugininmasterandsagahad no version at all; it now uses${jkube-maven-plugin-version}kafka-oauth-*0.15.0 -> 0.18.1. Renamed the property fromstrimzi.versiontostrimzi-kafka-oauth-version, since it versions the OAuth library and not the Strimzi operatornarayana-spring-boot-starter4.0.0 -> 4.1.1 (built against Spring Boot 4.1)swagger-codegen-maven-plugin3.0.52 -> 3.0.85. Since swagger-codegen-generators 1.0.53, thespringgenerator defaults tovalidationMode=strict, which importsJsonNullablefromorg.openapitools:jackson-databind-nullable.openapi-contract-firstnow setsvalidationMode=legacy, so the generated models are the same as before (compared with the 3.0.52 output; only whitespace and line order differ) and no extra dependency is neededopentelemetry-javaagent2.19.0 -> 2.33.1. One root property,opentelemetry-javaagent-version, replaces the separateopentelemetry-agent.version/opentelemetry-javaagent.versionproperties in observability-services, opentelemetry and rest-cxf-opentelemetryUnversioned plugins pinned
Without a version, Maven resolves whatever plugin release is newest, which may not match the Spring Boot version in use:
spring-boot-maven-plugin(opentelemetry/*, salesforce) ->${spring-boot-version}native-maven-plugin(aot-basic) -> 1.1.14, the version Spring Boot 4.1.2 usesCleanups
org.jolokia:jolokia-core1.7.1 frommetricsandsupervising-route-controller. Neither the code nor the configuration uses it, and Spring Boot 3+ no longer ships a Jolokia actuator endpoint (thejolokiaexample shows the supportedcamel-jolokia-startersetup)avro-version(kafka-avro),msal4j-version(mail-ms-exchange-oauth2),jakarta-servlet-api-version(saga)resilience4jclient2/service2 run on camel-main with SLF4J 2.x: switchedlog4j-slf4j-impl(SLF4J 1.x binding, ignored by SLF4J 2) tolog4j-slf4j2-implTesting
./mvnw -V clean installon the full reactor (Java 21, tests included): 86 tests run, 0 failures, 0 errors, 2 skippedkamelet-chucknorrisfails withNoClassDefFoundError: com/jayway/jsonpath/spi/json/Jackson3JsonProvider. It fails the same way on a cleanmain, so it is unrelated to this PR. Camel now usesjson-path3.0.0, but the Spring Boot 4.1.2 BOM manages 2.10.0openapi-contract-firstfailed on the first run because of the swagger-codegen change above. After thevalidationModefix it builds again./mvnw validateon the full reactor: no missing plugin version or groupId relocation warnings leftdependency:listchecks:artemisresolves onlyorg.apache.artemis:*:2.53.0observation/loggingtracerresolvesmicrometer-core1.17.2 andbrave6.3.1resilience4jclient2/service2 resolveslf4j-api2.0.20 withlog4j-slf4j2-impl2.25.5 as the only bindingClaude Code on behalf of Federico Mariani