This is an automated email from the ASF dual-hosted git repository. christophd pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel.git
commit 111155d124fa074d2e65aa5dddfc2a4690023af3 Author: Christoph Deppisch <[email protected]> AuthorDate: Thu Nov 12 09:21:27 2026 +0100 CAMEL-26764: Document annotation vs config appliesTo semantics Add a NOTE block to the upgrade guide clarifying that the annotation default (appliesTo = {}) is not the same as appliesTo: [] in the config file — the former is backward-compatible (no filtering), the latter restricts to own command only. Co-Authored-By: Claude Opus 4.6 <[email protected]> --- docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_24.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_24.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_24.adoc index 0f6161c68faf..7bb4ec4f9615 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_24.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_24.adoc @@ -1193,6 +1193,10 @@ When adding a plugin via `camel plugin add`, the `appliesTo` value from the list the configuration. After a plugin is downloaded for the first time, its `appliesTo` is learned from its `@CamelJBangPlugin` annotation and cached for subsequent invocations. +NOTE: The annotation default (`appliesTo = {}`) is not equivalent to `appliesTo: []` in the config file. +An unset annotation value means no filtering (backward compatible — the plugin is loaded for `run` and `export`), +whereas an explicit empty list in the config restricts the plugin to its own command only. + === camel-resilience4j, camel-microprofile-fault-tolerance - a circuit breaker in a doTry A circuit breaker in the steps of a `doTry` no longer ends that `doTry` for the steps after it. Before, when the
