[CAMEL-20524] Harmonize camel main configuration properties across runtimes - ASF JIRA

Voters

Watch issue

Watchers

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Closed
Priority: Minor
Resolution: Fixed
Affects Version/s: None
Fix Version/s: None
Component/s: camel-main, camel-quarkus, camel-spring-boot, camel-spring-boot-starters
Labels:
None

Estimated Complexity:
Unknown

Description

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.