Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
4.7.0
-
None
-
Unknown
Description
Something I came across when working on this task:
https://github.com/apache/camel-quarkus/issues/6083
In Camel Quarkus we have some logic to suppress Camel resolving properties from property sources other then those used by MicroProfile Config:
And there's a check for it in camel-main here:
However, when the 'dev' profile is activated, this check fails because the locations string is concatenated with other info. It'd probably be enough to tweak the if condition to also check if locations ends with ',false'.
Attachments
Issue Links
- links to