[
https://issues.apache.org/jira/browse/CAMEL-24378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18103499#comment-18103499
]
Cameron Fitzwater commented on CAMEL-24378:
-------------------------------------------
I understand the resource-dir flag – in fact, I put in that feature request ;).
This is a bit different, I think.
This request is for the ability to have a dir structure around the routes
themselves.
A simple test of:
1. camel init hello.yaml
2. run camel export
3. manually moved the file into a "test" sub-dir (
/src/main/resources/camel/test/hello.yaml).
4. run the app
The route was not taken into account as timer never fired.
> retain directory structure
> --------------------------
>
> Key: CAMEL-24378
> URL: https://issues.apache.org/jira/browse/CAMEL-24378
> Project: Camel
> Issue Type: New Feature
> Reporter: Cameron Fitzwater
> Priority: Major
>
> When utilizing camel cli, it would be beneficial if the directory path
> structure could be retained upon export.
> Currently, when running `camel export ... routes/to/file-a.camel.yaml`, the
> base files are placed directly in /src/main/resources/camel.
> This is fine for one or two files, but as it scales, keeping some level of
> structure is very helpful.
> The idea would be to retain the files with their entire dir structure, maybe
> by use of a new flag.
> _The one thing to account for is when relative paths are used, and how to
> handle that scenario (specifically, anything ../ bound). Potentially, by use
> of the new flag, it does not allow relative paths?_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
