[
https://issues.apache.org/jira/browse/CAMEL-24378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104179#comment-18104179
]
Cameron Fitzwater commented on CAMEL-24378:
-------------------------------------------
Ah, yes, your last comment may be getting to the core of what I'm actually
trying to solve for – and thus would not necessitate a feature request.
Based on your note, would the correct configuration option to use in this
scenario be: *camel.main.routes-include-pattern ?*
_Looks like default only looks at just camel/ (and must not be recursive), so I
could add camel/a, camel/b, etc._
I'm assuming I then would also want to enable :
*camel.main.routes-reload-directory-recursive*
Is there anything else I am missing? If not, consider this ticket to be closed
(and thank you).
https://camel.apache.org/camel-spring-boot/4.18.x/spring-boot.html#_sb_option_camel_main_routes-include-pattern
> 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)
