[
https://issues.apache.org/jira/browse/CAMEL-23658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-23658.
---------------------------------
Resolution: Fixed
> camel-jbang - Add camel dev as alias for camel run --dev
> --------------------------------------------------------
>
> Key: CAMEL-23658
> URL: https://issues.apache.org/jira/browse/CAMEL-23658
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 4.21.0
>
>
> Add camel dev as a shorthand alias for camel run --dev.
> Every modern framework has a short dev command:
> - npm run dev
> - mvn quarkus:dev
> - gradle bootRun
> camel dev would follow the same universal pattern. It is shorter, memorable,
> and what developers expect.
> Behavior:
> - camel dev (no args) should default to --source-dir=. (current directory) so
> it picks up all Camel files in the working directory. This means you can add,
> delete, and modify files and they are automatically hot-reloaded.
> - camel dev myRoute.yaml should work the same as camel run --dev myRoute.yaml
> - All camel run --dev flags should be supported
> This makes the workflow: cd into your project directory, type camel dev,
> start editing files. Same as npm run dev or mvn quarkus:dev.
> This also helps AI discoverability - AI coding assistants already assume
> camel dev exists (because it follows the universal pattern) and recommend it
> to users. Making it real means the recommendation works.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
