From c3bf8583c9af82ea38532ffa521f0354d44ba339 Mon Sep 17 00:00:00 2001 From: Dominik Jelinek Date: Fri, 4 Sep 2026 11:16:52 +0200 Subject: [PATCH] [backport camel-4.22.x] CAMEL-24628: camel-cli - camel dependency update propagate route files to export pipeline MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## Problem Since CAMEL-22544, `camel dependency update pom.xml route.camel.yaml` silently drops the route file and resolves zero dependencies. The `@Parameters(arity="1..*")` change causes all positional arguments to be consumed by `DependencyUpdate.targetFiles`. Non-update files (YAML/XML route definitions) are correctly classified but never propagated to `ExportBaseCommand.files`, so the export pipeline runs with no routes and discovers no components. This is a regression from Camel 4.20, where `arity="1"` let the second positional flow to `ExportBaseCommand.files` via `FilesConsumer`. IDE tooling uses this two-argument calling convention, as confirmed by prior issues CAMEL-22447 and CAMEL-22446. ## Fix Add an `else` branch in `DependencyUpdate.doCall()` that forwards non-target files (YAML, XML routes) to `this.files` for the export pipeline — exactly as the `@Parameters` description already promises. Add a test that passes both `pom.xml` and a route file as positional arguments to verify the route is used for dependency resolution. Co-authored-by: Claude Opus 4.6