Croway opened a new pull request, #2100: URL: https://github.com/apache/camel-spring-boot/pull/2100
## Description Companion to apache/camel#30200 for https://issues.apache.org/jira/browse/CAMEL-27030. Switch the hand-maintained servlet dependency in `camel-undertow-starter` from `io.undertow:undertow-servlet:${undertow-servlet-version}` to `io.undertow.ee:undertow-servlet:${undertow-ee-version}`. The Camel change removes the old parent property and exports `undertow-ee-version` through the generated `camel-dependencies` POM. With those updated Camel artifacts, the unchanged starter fails Maven model validation because its version expression is unresolved. Keeping the old artifact with a restored version would also retain the duplicate servlet implementations this migration addresses. Add a regression test that runs a Spring Boot-managed Camel Undertow consumer alongside a real asynchronous Undertow EE Servlet 6.1 deployment. It exercises the Camel Undertow producer against both servers and uses Servlet 6.1 APIs. This does not add a new server-starter dependency or change Camel route APIs/options. ## Validation - Reproduced the original Maven model-validation failure against the updated Camel dependencies. - Built the matching Camel dependency properties and BOM from the Camel PR, then built the 13-module CSB starter reactor from source. - `camel-undertow-starter` verification passed: existing SSL test and new Servlet 6.1 coexistence test, 2 tests, no failures or skips, on Java 25. - Dependency tree and runtime classpath contain Undertow EE 2.0.3.Final, core 2.4.4.Final, and Servlet API 6.1.0, without the old servlet artifact. - Regeneration and `git diff --check` passed. CI needs Camel snapshots containing apache/camel#30200. The local validation used artifacts built from that PR; coordinate the Camel and CSB changes before release. AI-assisted code and description prepared by Codex on behalf of Federico Mariani (@Croway). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
