CAMEL-22544: jbang dependency update supports multi-file and --scan-routes

[gnodet]

JIRA: CAMEL-22544

Summary

• Enhanced camel dependency update command to accept multiple target files (pom.xml or Java source files with //DEPS)
• Added --scan-routes flag to sync dependencies from route definitions:
  • Manages only org.apache.camel dependencies
  • Preserves non-Camel dependencies (e.g., guava, netty)
  • Removes unused Camel dependencies no longer needed by routes
  • Idempotent on re-execution (no duplicates)
• Route definition files (YAML, XML) passed as arguments are automatically classified and used as source files for the export pipeline
• In scan-routes mode, existing Camel //DEPS in Java target files are stripped before running the export pipeline, so only actual route-based dependencies are resolved
• Added input validation preventing mixed pom.xml and Java source files as update targets
• Fixed PrepareCamelJBangCommandsMojo regex to match this (not just main) as constructor arg, fixing stale metadata generation
• Fixed docs gulp race condition: added strict: false to gulp.src glob options so ENOENT errors during directory traversal (when test temp dirs are cleaned up concurrently) are warnings instead of failures
• Regenerated all jbang command metadata and docs

Test plan

• Existing DependencyUpdateTest (Maven pom.xml with quarkus, spring-boot, main runtimes) passes
• Scan-routes Maven tests use fixture files from src/test/resources/dependency-update/ (no Init+Export at runtime):
  • --scan-routes adds new deps from routes (Maven, all runtimes)
  • --scan-routes removes unused Camel deps from pom.xml
  • --scan-routes adds and removes deps simultaneously
• JBang //DEPS tests (inline fixtures):
  • Multi-file JBang //DEPS update
  • --scan-routes preserves non-Camel //DEPS in JBang files
  • --scan-routes is idempotent on re-execution

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[github-actions]

🧪 CI tested the following changed modules:

• docs
• dsl/camel-jbang/camel-jbang-core
• tooling/maven/camel-package-maven-plugin

ℹ️ Dependent modules were not tested because the total number of affected modules exceeded the threshold (50). Use the test-dependents label to force testing all dependents.

Build reactor — dependencies compiled but only changed modules were tested (6 modules)

• Camel :: Docs
• Camel :: Docs [pom]
• Camel :: JBang :: Core
• Camel :: JBang :: Core [jar]
• Camel :: Maven Plugins :: Camel Maven Package
• Camel :: Maven Plugins :: Camel Maven Package [maven-plugin]

[apupier]

What's the status? is it ready for another round of review? If yes, you should re-request review from claudio4j so that he is aware (and others too)

[gnodet]

Claude Code on behalf of Guillaume Nodet

@claudio4j Both review comments have been addressed in the latest push:

1. Fixture files instead of jbang init/export — The scan-routes Maven tests now use pre-built fixture files from src/test/resources/dependency-update/ (pom.xml per runtime + route YAML), avoiding jbang invocations in CI.
2. Single test class — Merged all tests from DependencyUpdateJBangTest into DependencyUpdateTest. Single test class now covers all scenarios.

Ready for another look when you get a chance.

[davsclaus]

Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified: docs/user-manual/modules/ROOT/pages/jbang-commands/camel-jbang-dependency-update.adoc
modified: dsl/camel-jbang/camel-jbang-core/src/generated/resources/META-INF/camel-jbang-commands-metadata.json
modified: tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/PrepareCamelJBangCommandsMojo.java