Skip to content

[CAMEL-FILE] Enhance logging in FileConsumer to aid debugging #18516

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

Brahmam0856
Copy link

This pull request introduces a minor but helpful enhancement in the camel-file component:

  • What was added: A new log statement in FileConsumer.java to output file names as they are picked up for processing.
  • Why: It aids developers in debugging and monitoring file route behavior without relying on external logging configuration.
  • Impact: Non-breaking change. Behavior remains identical, only log visibility is improved. Safe for all existing use cases.

Target

  • I checked that the commit is targeting the correct branch (main for Camel 4)

Tracking

  • No JIRA issue required—this is a trivial enhancement for visibility and developer experience.

Coding Standards & Style

  • Commit message is clear and scoped

  • Code was formatted and built using:

    bash
    mvn clean install -DskipTests

Copy link
Contributor

github-actions bot commented Jul 1, 2025

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

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

Copy link
Contributor

@oscerd oscerd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see nothing

@oscerd
Copy link
Contributor

oscerd commented Jul 2, 2025

Please, re-open once there is something to review. Thanks

@oscerd oscerd closed this Jul 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants