Skip to content

chore(ci): Add fallback for properties not in dependencyManagement#22040

Merged
gnodet merged 1 commit intomainfrom
detect-dependencies-fallback
Mar 16, 2026
Merged

chore(ci): Add fallback for properties not in dependencyManagement#22040
gnodet merged 1 commit intomainfrom
detect-dependencies-fallback

Conversation

@gnodet
Copy link
Contributor

@gnodet gnodet commented Mar 16, 2026

Summary

Follow-up to #22022. Some properties (e.g., mcp-java-sdk-version) are defined in the parent POM but used directly in module pom.xml files via ${prop}, not through the parent's <dependencyManagement> section.

The Toolbox tree-find approach only works for managed artifacts. For properties without a managed artifact, this adds a fallback that greps module pom.xml files for ${property} references.

Discovered from CI logs on PR #22018 where mcp-java-sdk-version was correctly detected as changed but no modules were found because the property is referenced directly in camel-openai/pom.xml rather than through dependency management.

Some properties (e.g., mcp-java-sdk-version) are defined in the parent
POM properties but used directly in module pom.xml files via ${prop},
not through the parent's dependencyManagement section.

The Toolbox tree-find approach only works for managed artifacts. For
properties without a managed artifact, fall back to grepping module
pom.xml files for ${property} references (the original approach, which
works correctly for this case).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@gnodet gnodet merged commit 8f900f1 into main Mar 16, 2026
2 checks passed
@github-actions
Copy link
Contributor

🌟 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.

vignesh-manel pushed a commit to vignesh-manel/camel that referenced this pull request Mar 18, 2026
…pache#22040)

Some properties (e.g., mcp-java-sdk-version) are defined in the parent
POM properties but used directly in module pom.xml files via ${prop},
not through the parent's dependencyManagement section.

The Toolbox tree-find approach only works for managed artifacts. For
properties without a managed artifact, fall back to grepping module
pom.xml files for ${property} references (the original approach, which
works correctly for this case).

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
@gnodet gnodet deleted the detect-dependencies-fallback branch March 20, 2026 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant