oscerd commented on PR #26463: URL: https://github.com/apache/camel/pull/26463#issuecomment-5828913797
Correction to my earlier note — the rebase did **not** clear it. The fresh run on the rebased head (befce7707, run 36108491740) fails the same way, so this reproduces on current `main` rather than being a stale artifact: ``` Could not find the selected project in the reactor: :camel-salesforce-maven-plugin-it ``` Root cause traced: `camel-salesforce-maven-plugin-it` is the artifactId of the maven-invoker IT projects under `components/camel-salesforce/camel-salesforce-maven-plugin/src/it/` (`simple-it`, `customized-types`). Those are standalone invoker projects, not modules in the reactor. Both declare `properties-maven-plugin` (pinned locally to `1.2.1` via their own `properties-maven-plugin-version` property), so the CI change-detection sees this bump's dependency in those `src/it/` poms and emits `-pl :camel-salesforce-maven-plugin-it`, which is not a reactor module — hence the failure. So the failure is in the module-selection step, not this bump: the root `properties-maven-plugin` upgrade (1.3.0 → 1.3.1) doesn't even reach those IT poms, which pin their own 1.2.1. The detection logic would need to skip `src/it/` invoker poms when mapping a changed dependency to reactor modules. @gnodet this is in the dependency-detection area you've been working (relates to the recent CI plumbing changes) — flagging since any bump of a dependency referenced from an invoker IT pom will hit the same thing. _This note was generated with AI assistance and issued by the human operator. Claude Code on behalf of oscerd_ -- 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]
