CAMEL-23226: Standardize error output to use printErr() in camel-jbang#22163
Merged
CAMEL-23226: Standardize error output to use printErr() in camel-jbang#22163
Conversation
Contributor
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
Contributor
|
🧪 CI tested the following changed modules:
All tested modules (26 modules)
|
oscerd
approved these changes
Mar 23, 2026
…g commands Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- InfraRun: Add missing else to avoid printing both error messages - Run: Keep warning as WARN (non-fatal IOException), not ERROR - Run: Convert missed startup failure message to printErr() Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
62ee227 to
3933312
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JIRA: CAMEL-23226
Summary
Camel JBang commands used three inconsistent patterns for reporting errors to the user:
printer().printErr()— the correct approach, uses the Printer abstraction withERROR:prefixSystem.err.println()— bypasses Printer, no consistent prefixprinter().println()— sends errors to stdout, invisible in stderr-only logsThis PR standardizes all error output to use
printer().printErr():action,catalog,config,infra,plugin,update, andversionpackagesConfigGetandPluginDeleteerror outputTest plan
ERROR:prefix in all fixed commandsConfigGetTestandPluginDeleteTestunit tests