Fix camel-jbang logging file appender and jbang java version option

[Croway]

Summary

• Add missing file appender to log4j2-no-color.properties — Since CAMEL-23226 changed loggingColor to auto-detect via EnvironmentHelper.isColorEnabled(), non-TTY environments (Docker containers, CI) use the no-color log config, which lacked the file appender. Logs went only to console, never to ~/.camel/<pid>.log, causing camel log to return empty and 38+ IT tests to timeout after 5 minutes.
• Fix jbang --java-version → --java — jbang does not recognize --java-version; the correct flag is --java. This caused 3 IT tests to fail when running with --camel-version pointing to older Camel versions.

Root cause analysis

Timeout failures (38 tests): Regression introduced by 3adff4a7fd4 (CAMEL-23226) which changed loggingColor default from true to EnvironmentHelper.isColorEnabled(). In Docker containers without TTY, this returns false, selecting log4j2-no-color.properties which had no file appender — unlike log4j2.properties which logs to both console and file.

--java-version failures (3 tests): Bug in c00319b34c6 (CAMEL-23235) which passed --java-version=21 to jbang, but jbang's actual option is --java.

Test plan

• Ran RunCommandITCase#initAndRunTest locally — was timing out, now passes in ~10s
• Ran RunCommandITCase#runSpecificVersionTest locally — was failing with Unknown option, now passes
• Ran VersionCommandITCase#executeAfterVersionSetTest locally — was failing, now passes
• All 4 tests: 0 failures (down from 41 failures in CI)

🤖 Generated with Claude Code

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

[Croway]

@smongiar @gnodet fyi

[github-actions]

🧪 CI tested the following changed modules:

• dsl/camel-jbang/camel-jbang-core
• dsl/camel-jbang/camel-jbang-plugin-kubernetes

All tested modules (26 modules)

• Camel :: Coverage
• Camel :: Coverage [pom]
• Camel :: JBang :: Core
• Camel :: JBang :: Core [jar]
• Camel :: JBang :: Integration tests
• Camel :: JBang :: Integration tests [jar]
• Camel :: JBang :: MCP
• Camel :: JBang :: MCP [jar]
• Camel :: JBang :: Main
• Camel :: JBang :: Main [jar]
• Camel :: JBang :: Plugin :: Edit
• Camel :: JBang :: Plugin :: Edit [jar]
• Camel :: JBang :: Plugin :: Generate
• Camel :: JBang :: Plugin :: Generate [jar]
• Camel :: JBang :: Plugin :: Kubernetes
• Camel :: JBang :: Plugin :: Kubernetes [jar]
• Camel :: JBang :: Plugin :: Route Parser
• Camel :: JBang :: Plugin :: Route Parser [jar]
• Camel :: JBang :: Plugin :: Testing
• Camel :: JBang :: Plugin :: Testing [jar]
• Camel :: JBang :: Plugin :: Validate
• Camel :: JBang :: Plugin :: Validate [jar]
• Camel :: Launcher
• Camel :: Launcher [jar]
• Camel :: Launcher :: Container
• Camel :: Launcher :: Container [pom]

[apupier]

should we change the --java-version parameter too which was added in the breaking commit in order to keep consistency between commands? c00319b

[Croway]

good point, in this case, --java is the JBang one, but I guess I can add an alias (for backward compatibility) to the Camel JBang Run and Export, wdyt?

[apupier]

I think it should work but worth to be tried, including when using "cross-versions" of Camel and Camel Jbang (which can be potentially used in from command-line and from VS Code integrations) because it reminds me simlar issues than afb0b1a when there was a renaming of property

[Croway]

good point, I just pushed a new commit that handle cross-version compatibility.. I actually never thought about cross-versions compatibility... well.. it is scary :D but I do think that most of the user stick on the latest Camel JBang version

[Croway]

@apupier @smongiar in the latest commit I've added the --java alias

[gnodet]

Good fix for two clear regressions. Root cause analysis in the PR description is excellent.

A few observations:

Generated files need regeneration — The picocli annotation changes (adding --java alias) need the generated metadata and docs updated. Currently camel-jbang-commands-metadata.json still shows only --java-version for the export/sbom commands, and the generated docs in docs/user-manual/modules/ROOT/pages/jbang-commands/ also only reference --java-version. The CI "uncommitted changes" check will likely flag this. Run:

mvn install -B -pl dsl/camel-jbang/camel-jbang-core -DskipTests

and commit the regenerated files.

Pre-existing: color config's file appender uses ANSI patterns — Not introduced by this PR, but worth noting: log4j2.properties writes %style{...} / %highlight{...} patterns to the file appender, so ~/.camel/{pid}.log ends up with ANSI escape codes. The no-color fix correctly uses plain patterns for the file, which is actually better behavior.

Claude Code on behalf of Guillaume Nodet