gnodet opened a new pull request, #24402: URL: https://github.com/apache/camel/pull/24402
## Summary _Claude Code on behalf of Guillaume Nodet_ Fix flaky `ExportTest` and `DependencyUpdateTest` in `camel-jbang-core` that intermittently fail for the Spring Boot runtime parameterization. - **Root cause**: `CatalogLoader.loadSpringBootCatalog()` always downloads `camel-catalog-provider-springboot` from remote repos. Unlike `loadCatalog()` for the main runtime (which short-circuits when the requested version matches the bundled catalog), the Spring Boot path has no such optimization. The `camel-catalog-provider-springboot` artifact comes from the **separate** `camel-spring-boot` project, whose SNAPSHOT may not be deployed to Apache Snapshots at any given time. - **Fix**: Pin Spring Boot test parameterizations to a released Camel version (`4.13.0`) via `--camel-version`. Released versions are always available on Maven Central, making these tests deterministic. Tests that already specify `--camel-version` (like `shouldExportDifferentVersion`) are left unchanged via a `containsCamelVersion()` guard. - **Scope**: Only test code is modified — no production behavior changes. The tests verify POM generation and dependency mapping logic, not version resolution itself. ### Observed failure This was observed in [PR #24399](https://github.com/apache/camel/pull/24399) CI where all 23 Spring Boot (`[2]`) parameterized test cases failed with: ``` Cannot download org.apache.camel.springboot:camel-catalog-provider-springboot:4.22.0-SNAPSHOT ``` ## Test plan - [ ] CI passes for `camel-jbang-core` module tests - [ ] Spring Boot `[2]` parameterized tests no longer fail due to SNAPSHOT download issues - [ ] Main `[3]` and Quarkus `[1]` test parameterizations remain unaffected 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
