Croway opened a new pull request, #2070: URL: https://github.com/apache/camel-spring-boot/pull/2070
Fixes [CAMEL-26534](https://issues.apache.org/jira/browse/CAMEL-26534). `CamelOpenfeatureIT` fails in [Camel-Spring-Boot Daily #439](https://ci-builds.apache.org/job/Camel/job/Camel-Spring-Boot%20Daily/job/main/439/) (builds35): ``` No versions available for dev.openfeature.contrib.tools:flagd-core:jar:[3.0.0,4.0.0) within specified range ``` ### Cause - Camel bumped `flagd` from 0.14.2 to 0.15.0 on 2026-11-02. 0.15.0 declares `flagd-core` as `[3.0.0,4.0.0)` (0.14.2 declared `[2.0.0,3.0.0)`). The reactor build isn't affected because camel-parent pins `flagd-core`, but the generated archetype project only imports `camel-spring-boot-bom`, so it has to resolve the range. - `ArchetypeGenerationExtension.runMaven` passes `-nsu` (added in #2024). In Maven 3.9.11 that sets the session update policy to `never`, and Maven Resolver 1.9.24 applies it to release repositories as well as snapshot ones. The range is therefore matched against the `flagd-core` metadata the agent's shared `~/.m2` already holds. On builds35 that metadata dates from before 3.0.0 was released (2026-10-15), and it is never refreshed. ### Change - Drop `-nsu` from the nested Maven runs. The javadoc and the module README now explain why it is not used. - Before #2024 neither nested run used `-nsu`, so this restores the earlier update behavior. Generating the template once, the 1 GB heap and the captured output from #2024 stay. ### Cost and trade-off - **Cost:** the reactor build runs with `-U`, so the Camel core snapshots have already been checked for the day. What's left is about one metadata request per IT, for its own starter, once per day. A request to repository.apache.org takes 150–300 ms. - **Trade-off:** an IT can now pick up a starter published by the Snapshot Deploy job if that copy is newer than the one the reactor installed. Both jobs build `main`, so in practice it's the same code. ### Testing - **Reproduction with Maven 3.9.11:** a project depending on `flagd:0.15.0`, with a local repository seeded with `flagd-core` metadata from before 3.0.0 and a last check on 2026-10-01. - `-q -B -nsu dependency:build-classpath` fails with the same error as #439. - Without `-nsu`, Maven refreshes the metadata and resolves `flagd-core-3.0.0.jar`. - **Module:** `tests/camel-itest-spring-boot` compiles. - **Not run locally:** the full IT suite. The check that matters is `CamelOpenfeatureIT` on the next Daily run on builds35. - **No new test:** the harness has no unit tests, and reproducing this needs a nested Maven run against a seeded local repository plus network access. `CamelOpenfeatureIT` covers it on CI. _Claude Code (Claude Opus 5.5) on behalf of Federico Mariani_ -- 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]
