[
https://issues.apache.org/jira/browse/CAMEL-22360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18023829#comment-18023829
]
Cameron Fitzwater commented on CAMEL-22360:
-------------------------------------------
I agree with Claus – though, I will iterate that the _.camel-sources file
solution mentioned_ above works really well.
Seeing some sort of solution that better supports CI-capabilities is likely
more important here than anything else. If this _.camel-sources file_ was able
to use * expression notation that camel run/export could source, that would be
icing on the cake.
> camel jbang add recursive flag
> ------------------------------
>
> Key: CAMEL-22360
> URL: https://issues.apache.org/jira/browse/CAMEL-22360
> Project: Camel
> Issue Type: New Feature
> Components: camel-jbang
> Reporter: Cameron Fitzwater
> Assignee: Radovan Netuka
> Priority: Minor
>
> *Request:*
> Add {{--recursive}} flag to {{camel run}} and {{camel export}} commands for
> subdirectory file discovery.
>
> *Problem:*
> Currently, {{camel run *}} and {{camel export *}} commands only discover
> files at the base level of the current (or specified) directory and do not
> recursively search subdirectories.
> This limitation:
> # *Prevents CI/CD standardization* - Requires project-specific build
> commands instead of a standardized approach
> # *Restricts project structure flexibility* - Forces all integration files
> to be in a single directory if trying to standardize the CI
>
> *Expected behavior with {{{}--recursive{}}}:*
> project/
> ├── main.yaml # ✅ Found
> ├── routes/
> │ ├── dispatch-routes.yaml # ✅ Found with --recursive
> │ └── market-routes.yaml # ✅ Found with --recursive
> ├── shared/
> │ └── common-routes.yaml # ✅ Found with --recursive
> └── src/
> └── main/
> └── java/
> └── handlers/
> └── MyHandler.java # ✅ Found with --recursive
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
