This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch jt
in repository https://gitbox.apache.org/repos/asf/camel.git

commit 49ca853beeaf73eeb58d93a2af207bd5ad73bf84
Author: Claus Ibsen <[email protected]>
AuthorDate: Thu Aug 14 09:59:20 2025 +0200

    CAMEL-22205: camel-jbang: Document all camel.jbang options for tooling
---
 docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc | 4 ++++
 1 file changed, 4 insertions(+)

diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
index 6ee8c3bd4d4..2637c44bbd9 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
@@ -64,6 +64,10 @@ this during export.
 
 Notice when exporting to kubernetes then `camel-observabilities-services` is 
always enabled.
 
+When controlling Camel JBang exports with configuration in 
`application.properties` then
+there was a duplicate option (`camel.jbang.repositories` and 
`camel.jbang.repos`) which has been fixed to
+be only `camel.jbang.repos`.
+
 === camel-google
 
 The scopes parameter for camel-google-calendar, camel-google-calendar-streams, 
camel-google-drive, camel-google-mail, camel-google-mail-streams and 
camel-google-sheets-streams has been defined as String instead of 
Collection<String>. For the migration users will need to, eventually, define 
scopes as a comma separated list of scopes instead of a Collection instance. 
For more information the related issue is CAMEL-22247.

Reply via email to