Skip to content

fix(#1581): Fix misleading log output when waitForRunningState is false#1585

Merged
christophd merged 1 commit into
mainfrom
fix/1581
Jul 8, 2026
Merged

fix(#1581): Fix misleading log output when waitForRunningState is false#1585
christophd merged 1 commit into
mainfrom
fix/1581

Conversation

@christophd

@christophd christophd commented Jul 8, 2026

Copy link
Copy Markdown
Member

Summary

  • Moves the "Waiting for the Camel integration to be running" log message inside the waitForRunningState conditional so it only appears when the action actually waits
  • Adds a distinct log message when waitForRunningState is false: "Started Camel integration — not waiting for running state"

Fixes #1581

Test plan

  • Module builds successfully (mvn -DskipTests install in endpoints/citrus-camel)
  • Full reactor build passes (mvn clean install -DskipTests)
  • Manual verification: run a Camel integration with waitForRunningState: false and confirm the new log message appears

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@christophd christophd merged commit 5e9b0bb into main Jul 8, 2026
1 check passed
@christophd christophd deleted the fix/1581 branch July 8, 2026 17:43
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.

Fix misleading log output when Camel waitForRunningState is false

1 participant