Repository navigation
[4.18.x] Regen BOMs for Camel 4.18.6-SNAPSHOT (fixes Vert.x NoSuchMethodError on CI) - #2059
Merged
Croway merged 1 commit intoOct 26, 2026
Conversation
…mel 4.18.6-SNAPSHOT After the 4.18.5 release the generated BOMs still pinned every org.apache.camel artifact to the released 4.18.5, so the build mixed 4.18.5 and 4.18.6-SNAPSHOT Camel jars. Since the upstream Vert.x 4.5.35 upgrade this puts camel-vertx-common 4.18.5 (vertx-core 4.5.26) next to vertx-web 4.5.35, which breaks JsonPathPlatformHttpTest, VertxWebsocketSSLTest and VertxWebsocketSSLGlobalTest with NoSuchMethodError.
davsclaus
approved these changes
Oct 26, 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
Since #264 (Oct 21), the Camel-Spring-Boot Daily
camel-spring-boot-4.18.xjob fails every run onJsonPathPlatformHttpTest,VertxWebsocketSSLTestandVertxWebsocketSSLGlobalTest:Cause: after the 4.18.5 release, the generated
camel-spring-boot-dependenciesandcamel-spring-boot-bomwere never regenerated. They still pinned all 517org.apache.camelartifacts to the released4.18.5, whilecamel-versionis4.18.6-SNAPSHOT, so CI mostly tested against the 4.18.5 release. When Camel 4.18.x upgraded Vert.x to 4.5.35 (apache/camel#28121),camel-platform-http-vertx:4.18.6-SNAPSHOT(vertx-web 4.5.35) ended up next tocamel-vertx-common:4.18.5(vertx-core 4.5.26).Change: this is the usual post-release regen, produced by the BOM generators (
tooling/camel-spring-boot-dependencies-generatorandtooling/camel-spring-boot-bom-generator). The diff only changes versions,4.18.5→4.18.6-SNAPSHOT.Test plan
mvn dependency:treeoncamel-vertx-websocket-starter:vertx-corenow resolves to 4.5.35 (it was 4.5.26)JsonPathPlatformHttpTest,VertxWebsocketSSLTestandVertxWebsocketSSLGlobalTestpass locallyClaude Code (Opus 5.5) on behalf of Federico Mariani