[
https://issues.apache.org/jira/browse/CAMEL-20524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed CAMEL-20524.
-----------------------------------
Resolution: Fixed
> Harmonize camel main configuration properties across runtimes
> -------------------------------------------------------------
>
> Key: CAMEL-20524
> URL: https://issues.apache.org/jira/browse/CAMEL-20524
> Project: Camel
> Issue Type: Improvement
> Components: camel-main, camel-quarkus, camel-spring-boot,
> camel-spring-boot-starters
> Reporter: Luca Burgazzoli
> Assignee: Guillaume Nodet
> Priority: Minor
>
> The camel-main module was originally designed to run make it easy to run
> camel standalone without the need of a specific runtime (spring-boot,
> quarkus, etc), but now camel-main is also a core component of camel-quarkus
> and camel-spring-boot.
> camel-main also offers a number of properties that can be configured to
> configure camel-main, however, the runtimes may use some slight different
> property naming/namespaces making things a little bit confusing.
> As an example, camel-main defines a camel.main.routes-include-pattern
> property to let camel discover routes, however in camel-spring-boot the same
> property is camel.springboot..routes-include-pattern
> Ideally, runtimes should honor camel-main property and reserve some specific
> namespaces (i.e. camel.quarkus camel.springboot) for runtime specific options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
