[
https://issues.apache.org/jira/browse/CAMEL-26467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-26467 started by Claus Ibsen.
-------------------------------------------
> camel-jbang - A file that does not exist exits with 66 (EX_NOINPUT), not 3
> --------------------------------------------------------------------------
>
> Key: CAMEL-26467
> URL: https://issues.apache.org/jira/browse/CAMEL-26467
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> The exit codes of the Camel CLI (CAMEL-25388, new in 4.24) follow the usual
> Linux conventions, so that scripts and AI agents can read them without the
> docs: {{2}} usage, {{70}} {{EX_SOFTWARE}}, {{124}} as GNU {{timeout}}.
> Code {{3}} ("not found") covers two different cases:
> * a running integration, route, service, plugin or catalog entry that is not
> there. This matches the LSB convention, which {{systemctl status}} also uses
> for a service that is not running;
> * a file or directory given on the command line that does not exist. For
> that, {{3}} is no convention. The standard code for missing input is {{66}}
> ({{EX_NOINPUT}} from {{sysexits.h}}).
> A missing file or path should exit with {{66}}, and {{3}} should stay for
> what is not running or not there. 4.24 is not released yet, so no user relies
> on {{3}} for a file.
> _Claude Code on behalf of davsclaus (Claus Ibsen)_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
