[jira] [Created] (CAMEL-18511) Camel-Azure-Key-Vault: Create a task looking for secrets update in Eventhubs
Andrea Cosentino created CAMEL-18511: Summary: Camel-Azure-Key-Vault: Create a task looking for secrets update in Eventhubs Key: CAMEL-18511 URL: https://issues.apache.org/jira/browse/CAMEL-18511 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18510) camel-jbang - camel bind may not work with --local-kamelet-dir
[ https://issues.apache.org/jira/browse/CAMEL-18510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17605119#comment-17605119 ] Claus Ibsen commented on CAMEL-18510: - TODO: camel init kamelet should support sink vs source > camel-jbang - camel bind may not work with --local-kamelet-dir > -- > > Key: CAMEL-18510 > URL: https://issues.apache.org/jira/browse/CAMEL-18510 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 3.18.2 >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.18.3, 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18510) camel-jbang - camel bind may not work with --local-kamelet-dir
[ https://issues.apache.org/jira/browse/CAMEL-18510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17605112#comment-17605112 ] Claus Ibsen commented on CAMEL-18510: - Also it should be possible to use current dir as local kamelet dir > camel-jbang - camel bind may not work with --local-kamelet-dir > -- > > Key: CAMEL-18510 > URL: https://issues.apache.org/jira/browse/CAMEL-18510 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 3.18.2 >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.18.3, 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18510) camel-jbang - camel bind may not work with --local-kamelet-dir
[ https://issues.apache.org/jira/browse/CAMEL-18510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17605113#comment-17605113 ] Claus Ibsen commented on CAMEL-18510: - camel init my-sink.kamelet.yaml camel bind timer-source my-sink mybinding.yaml --local-kamelet-dir=. > camel-jbang - camel bind may not work with --local-kamelet-dir > -- > > Key: CAMEL-18510 > URL: https://issues.apache.org/jira/browse/CAMEL-18510 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 3.18.2 >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.18.3, 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18510) camel-jbang - camel bind may not work with --local-kamelet-dir
Claus Ibsen created CAMEL-18510: --- Summary: camel-jbang - camel bind may not work with --local-kamelet-dir Key: CAMEL-18510 URL: https://issues.apache.org/jira/browse/CAMEL-18510 Project: Camel Issue Type: Bug Components: camel-jbang Affects Versions: 3.18.2 Reporter: Claus Ibsen Fix For: 3.18.3, 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18509) use servlet transport for camel-cxf spring boot test
[ https://issues.apache.org/jira/browse/CAMEL-18509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Yue Fang updated CAMEL-18509: - Fix Version/s: 3.18.3 3.19.0 > use servlet transport for camel-cxf spring boot test > > > Key: CAMEL-18509 > URL: https://issues.apache.org/jira/browse/CAMEL-18509 > Project: Camel > Issue Type: Test > Components: came-cxf, camel-spring-boot, tests >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > Fix For: 3.18.3, 3.19.0 > > > Use SB container servlet transport(spring-boot-starter-web) instead of the > embeded undertow server -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18509) use servlet transport for camel-cxf spring boot test
[ https://issues.apache.org/jira/browse/CAMEL-18509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Yue Fang reassigned CAMEL-18509: Assignee: Freeman Yue Fang > use servlet transport for camel-cxf spring boot test > > > Key: CAMEL-18509 > URL: https://issues.apache.org/jira/browse/CAMEL-18509 > Project: Camel > Issue Type: Test > Components: came-cxf, camel-spring-boot, tests >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > > Use SB container servlet transport(spring-boot-starter-web) instead of the > embeded undertow server -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18509) use servlet transport for camel-cxf spring boot test
Freeman Yue Fang created CAMEL-18509: Summary: use servlet transport for camel-cxf spring boot test Key: CAMEL-18509 URL: https://issues.apache.org/jira/browse/CAMEL-18509 Project: Camel Issue Type: Test Components: came-cxf, camel-spring-boot, tests Reporter: Freeman Yue Fang Use SB container servlet transport(spring-boot-starter-web) instead of the embeded undertow server -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18508) camel-jbang - User config file
Claus Ibsen created CAMEL-18508: --- Summary: camel-jbang - User config file Key: CAMEL-18508 URL: https://issues.apache.org/jira/browse/CAMEL-18508 Project: Camel Issue Type: New Feature Components: camel-jbang Reporter: Claus Ibsen Fix For: 3.20.0 It would be good to allow a user config file, where you can store various default values and versions for camel-jbang, such as - 3rd party maven repos - specific camel version to use - specific spring boot / quarkus version to use - etc. The config should contain key=value pairs as .properties which maps to CLI arguments when using the camel CLI. We can have commands ala: camel config list camel config get x camel config set x=y camel config unset x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18506) Migrate components away from Async HTTP Client
[ https://issues.apache.org/jira/browse/CAMEL-18506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18506: Fix Version/s: 3.x > Migrate components away from Async HTTP Client > -- > > Key: CAMEL-18506 > URL: https://issues.apache.org/jira/browse/CAMEL-18506 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.x > > > The project Async HTTP Client is likely > [unmaintained|https://github.com/AsyncHttpClient/async-http-client/commit/c959fa0483adb4a71fbccc5be94d8b6faa4f74be]. > We should migrate the following components to a different HTTP client: > * camel-ahc (to be removed ... see CAMEL-18496) > * camel-atmosphere-websocket (test scope) > * camel-elytron (test scope) > * camel-telegram ({*}runtime{*} scope) > * camel-undertow (test scope) > * camel-websocket (test scope) > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-11252) camel-core : allow to retrieve components/endpoints/etc list with a predicate
[ https://issues.apache.org/jira/browse/CAMEL-11252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-11252: --- Assignee: Nicolas Filotto > camel-core : allow to retrieve components/endpoints/etc list with a predicate > - > > Key: CAMEL-11252 > URL: https://issues.apache.org/jira/browse/CAMEL-11252 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Luca Burgazzoli >Assignee: Nicolas Filotto >Priority: Major > Fix For: 3.x > > > As today components/endpoints and so on can be retrieved/removed from the > camel context by id but it would be nice to have a more flexible way to > retrieve them like: > {code:java} > List components = context.getComponents(id, component -> { > return component instanceof IdAware; > }); > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-11252) camel-core : allow to retrieve components/endpoints/etc list with a predicate
[ https://issues.apache.org/jira/browse/CAMEL-11252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-11252. - Fix Version/s: 3.19.0 (was: 3.x) Resolution: Fixed > camel-core : allow to retrieve components/endpoints/etc list with a predicate > - > > Key: CAMEL-11252 > URL: https://issues.apache.org/jira/browse/CAMEL-11252 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Luca Burgazzoli >Assignee: Nicolas Filotto >Priority: Major > Fix For: 3.19.0 > > > As today components/endpoints and so on can be retrieved/removed from the > camel context by id but it would be nice to have a more flexible way to > retrieve them like: > {code:java} > List components = context.getComponents(id, component -> { > return component instanceof IdAware; > }); > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18505) Camel-coap: Version conflict (californium-legal and element-connector)
[ https://issues.apache.org/jira/browse/CAMEL-18505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18505. - Resolution: Fixed > Camel-coap: Version conflict (californium-legal and element-connector) > -- > > Key: CAMEL-18505 > URL: https://issues.apache.org/jira/browse/CAMEL-18505 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-coap >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.19.0 > > > Recent update of Scandium to 2.7.3 created 2 version conflicts in camel-coap. > Build of camel-quarkus extension copa fails with: > {code:java} > Dependency convergence error for > org.eclipse.californium:californium-legal:2.7.2 paths to dependency are: > 2022-09-14T07:34:24.8326810Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8327409Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8327954Z > +-org.eclipse.californium:californium-core:2.7.2 > 2022-09-14T07:34:24.8328418Z > +-org.eclipse.californium:californium-legal:2.7.2 > 2022-09-14T07:34:24.8328734Z and > 2022-09-14T07:34:24.8329134Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8329585Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8330014Z > +-org.eclipse.californium:californium-core:2.7.2 > 2022-09-14T07:34:24.8330456Z > +-org.eclipse.californium:element-connector:2.7.2 > 2022-09-14T07:34:24.8330902Z > +-org.eclipse.californium:californium-legal:2.7.2 > 2022-09-14T07:34:24.8331209Z and > 2022-09-14T07:34:24.8331597Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8332051Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8332467Z +-org.eclipse.californium:scandium:2.7.3 > 2022-09-14T07:34:24.8332906Z > +-org.eclipse.californium:californium-legal:2.7.3 > 2022-09-14T07:34:24.8333204Z and > 2022-09-14T07:34:24.8333592Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8334030Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8334476Z > +-org.eclipse.californium:element-connector-tcp-netty:2.7.2 > 2022-09-14T07:34:24.8334946Z > +-org.eclipse.californium:californium-legal:2.7.2 > 2022-09-14T07:34:24.8335189Z > 2022-09-14T07:34:24.8335402Z [WARNING] > 2022-09-14T07:34:24.8335890Z Dependency convergence error for > org.eclipse.californium:element-connector:2.7.2 paths to dependency are: > 2022-09-14T07:34:24.8336425Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8336868Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8337522Z > +-org.eclipse.californium:californium-core:2.7.2 > 2022-09-14T07:34:24.8337984Z > +-org.eclipse.californium:element-connector:2.7.2 > 2022-09-14T07:34:24.8338286Z and > 2022-09-14T07:34:24.8338680Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8339126Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8339605Z +-org.eclipse.californium:scandium:2.7.3 > 2022-09-14T07:34:24.8340053Z > +-org.eclipse.californium:element-connector:2.7.3 > 2022-09-14T07:34:24.8340338Z and > 2022-09-14T07:34:24.8340717Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8341155Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8341615Z > +-org.eclipse.californium:element-connector-tcp-netty:2.7.2 > 2022-09-14T07:34:24.8342089Z > +-org.eclipse.californium:element-connector:2.7.2 {code} > Correct solution should be to move californium:element-connector and > californium:californium-legal: to version 2.7.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18507) camel-resilience4j - Add option to throw exception if CB rejected due to half-open/open state
[ https://issues.apache.org/jira/browse/CAMEL-18507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18507. - Resolution: Fixed > camel-resilience4j - Add option to throw exception if CB rejected due to > half-open/open state > - > > Key: CAMEL-18507 > URL: https://issues.apache.org/jira/browse/CAMEL-18507 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.3, 3.19.0 > > > Reported in community on mailing list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18507) camel-resilience4j - Add option to throw exception if CB rejected due to half-open/open state
[ https://issues.apache.org/jira/browse/CAMEL-18507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18507: Fix Version/s: 3.18.3 > camel-resilience4j - Add option to throw exception if CB rejected due to > half-open/open state > - > > Key: CAMEL-18507 > URL: https://issues.apache.org/jira/browse/CAMEL-18507 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.3, 3.19.0 > > > Reported in community on mailing list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18507) camel-resilience4j - Add option to throw exception if CB rejected due to half-open/open state
[ https://issues.apache.org/jira/browse/CAMEL-18507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-18507: --- Assignee: Claus Ibsen > camel-resilience4j - Add option to throw exception if CB rejected due to > half-open/open state > - > > Key: CAMEL-18507 > URL: https://issues.apache.org/jira/browse/CAMEL-18507 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > Reported in community on mailing list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18507) camel-resilience4j - Add option to throw exception if CB rejected due to half-open/open state
Claus Ibsen created CAMEL-18507: --- Summary: camel-resilience4j - Add option to throw exception if CB rejected due to half-open/open state Key: CAMEL-18507 URL: https://issues.apache.org/jira/browse/CAMEL-18507 Project: Camel Issue Type: Improvement Reporter: Claus Ibsen Fix For: 3.19.0 Reported in community on mailing list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18456) camel-test-infra: investigate consolidating usages of web server and servlets
[ https://issues.apache.org/jira/browse/CAMEL-18456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-18456. -- Fix Version/s: 3.19.0 (was: 3.x) Resolution: Fixed Created a new test infra component and migrated most of the usages with low coupling to this component. A few usages that were either deprecated (like cmis) or too tightly coupled (camel-websocket, etc) were not migrated. > camel-test-infra: investigate consolidating usages of web server and servlets > - > > Key: CAMEL-18456 > URL: https://issues.apache.org/jira/browse/CAMEL-18456 > Project: Camel > Issue Type: Task > Components: camel-test-infra >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.19.0 > > > There are many tests using Jetty, Undertow, Tomcat and others to run web > servers and/or servlet containers. Investigate consolidating this code into a > test infra module and cleaning up the components. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18506) Migrate components away from Async HTTP Client
[ https://issues.apache.org/jira/browse/CAMEL-18506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17604271#comment-17604271 ] Otavio Rodolfo Piske commented on CAMEL-18506: -- [~davsclaus] [~acosentino] FYI, more stuff to cleanup. > Migrate components away from Async HTTP Client > -- > > Key: CAMEL-18506 > URL: https://issues.apache.org/jira/browse/CAMEL-18506 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Priority: Major > > The project Async HTTP Client is likely > [unmaintained|https://github.com/AsyncHttpClient/async-http-client/commit/c959fa0483adb4a71fbccc5be94d8b6faa4f74be]. > We should migrate the following components to a different HTTP client: > * camel-ahc (to be removed ... see CAMEL-18496) > * camel-atmosphere-websocket (test scope) > * camel-elytron (test scope) > * camel-telegram ({*}runtime{*} scope) > * camel-undertow (test scope) > * camel-websocket (test scope) > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18506) Migrate components away from Async HTTP Client
[ https://issues.apache.org/jira/browse/CAMEL-18506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske reassigned CAMEL-18506: Assignee: Otavio Rodolfo Piske > Migrate components away from Async HTTP Client > -- > > Key: CAMEL-18506 > URL: https://issues.apache.org/jira/browse/CAMEL-18506 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > > The project Async HTTP Client is likely > [unmaintained|https://github.com/AsyncHttpClient/async-http-client/commit/c959fa0483adb4a71fbccc5be94d8b6faa4f74be]. > We should migrate the following components to a different HTTP client: > * camel-ahc (to be removed ... see CAMEL-18496) > * camel-atmosphere-websocket (test scope) > * camel-elytron (test scope) > * camel-telegram ({*}runtime{*} scope) > * camel-undertow (test scope) > * camel-websocket (test scope) > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18506) Migrate components away from Async HTTP Client
Otavio Rodolfo Piske created CAMEL-18506: Summary: Migrate components away from Async HTTP Client Key: CAMEL-18506 URL: https://issues.apache.org/jira/browse/CAMEL-18506 Project: Camel Issue Type: Task Reporter: Otavio Rodolfo Piske The project Async HTTP Client is likely [unmaintained|https://github.com/AsyncHttpClient/async-http-client/commit/c959fa0483adb4a71fbccc5be94d8b6faa4f74be]. We should migrate the following components to a different HTTP client: * camel-ahc (to be removed ... see CAMEL-18496) * camel-atmosphere-websocket (test scope) * camel-elytron (test scope) * camel-telegram ({*}runtime{*} scope) * camel-undertow (test scope) * camel-websocket (test scope) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18505) Camel-coap: Version conflict (californium-legal and element-connector)
[ https://issues.apache.org/jira/browse/CAMEL-18505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18505: Fix Version/s: 3.19.0 > Camel-coap: Version conflict (californium-legal and element-connector) > -- > > Key: CAMEL-18505 > URL: https://issues.apache.org/jira/browse/CAMEL-18505 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-coap >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.19.0 > > > Recent update of Scandium to 2.7.3 created 2 version conflicts in camel-coap. > Build of camel-quarkus extension copa fails with: > {code:java} > Dependency convergence error for > org.eclipse.californium:californium-legal:2.7.2 paths to dependency are: > 2022-09-14T07:34:24.8326810Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8327409Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8327954Z > +-org.eclipse.californium:californium-core:2.7.2 > 2022-09-14T07:34:24.8328418Z > +-org.eclipse.californium:californium-legal:2.7.2 > 2022-09-14T07:34:24.8328734Z and > 2022-09-14T07:34:24.8329134Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8329585Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8330014Z > +-org.eclipse.californium:californium-core:2.7.2 > 2022-09-14T07:34:24.8330456Z > +-org.eclipse.californium:element-connector:2.7.2 > 2022-09-14T07:34:24.8330902Z > +-org.eclipse.californium:californium-legal:2.7.2 > 2022-09-14T07:34:24.8331209Z and > 2022-09-14T07:34:24.8331597Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8332051Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8332467Z +-org.eclipse.californium:scandium:2.7.3 > 2022-09-14T07:34:24.8332906Z > +-org.eclipse.californium:californium-legal:2.7.3 > 2022-09-14T07:34:24.8333204Z and > 2022-09-14T07:34:24.8333592Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8334030Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8334476Z > +-org.eclipse.californium:element-connector-tcp-netty:2.7.2 > 2022-09-14T07:34:24.8334946Z > +-org.eclipse.californium:californium-legal:2.7.2 > 2022-09-14T07:34:24.8335189Z > 2022-09-14T07:34:24.8335402Z [WARNING] > 2022-09-14T07:34:24.8335890Z Dependency convergence error for > org.eclipse.californium:element-connector:2.7.2 paths to dependency are: > 2022-09-14T07:34:24.8336425Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8336868Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8337522Z > +-org.eclipse.californium:californium-core:2.7.2 > 2022-09-14T07:34:24.8337984Z > +-org.eclipse.californium:element-connector:2.7.2 > 2022-09-14T07:34:24.8338286Z and > 2022-09-14T07:34:24.8338680Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8339126Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8339605Z +-org.eclipse.californium:scandium:2.7.3 > 2022-09-14T07:34:24.8340053Z > +-org.eclipse.californium:element-connector:2.7.3 > 2022-09-14T07:34:24.8340338Z and > 2022-09-14T07:34:24.8340717Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8341155Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8341615Z > +-org.eclipse.californium:element-connector-tcp-netty:2.7.2 > 2022-09-14T07:34:24.8342089Z > +-org.eclipse.californium:element-connector:2.7.2 {code} > Correct solution should be to move californium:element-connector and > californium:californium-legal: to version 2.7.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18505) Camel-coap: Version conflict (californium-legal and element-connector)
[ https://issues.apache.org/jira/browse/CAMEL-18505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18505: Issue Type: Dependency upgrade (was: Bug) > Camel-coap: Version conflict (californium-legal and element-connector) > -- > > Key: CAMEL-18505 > URL: https://issues.apache.org/jira/browse/CAMEL-18505 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-coap >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > > Recent update of Scandium to 2.7.3 created 2 version conflicts in camel-coap. > Build of camel-quarkus extension copa fails with: > {code:java} > Dependency convergence error for > org.eclipse.californium:californium-legal:2.7.2 paths to dependency are: > 2022-09-14T07:34:24.8326810Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8327409Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8327954Z > +-org.eclipse.californium:californium-core:2.7.2 > 2022-09-14T07:34:24.8328418Z > +-org.eclipse.californium:californium-legal:2.7.2 > 2022-09-14T07:34:24.8328734Z and > 2022-09-14T07:34:24.8329134Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8329585Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8330014Z > +-org.eclipse.californium:californium-core:2.7.2 > 2022-09-14T07:34:24.8330456Z > +-org.eclipse.californium:element-connector:2.7.2 > 2022-09-14T07:34:24.8330902Z > +-org.eclipse.californium:californium-legal:2.7.2 > 2022-09-14T07:34:24.8331209Z and > 2022-09-14T07:34:24.8331597Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8332051Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8332467Z +-org.eclipse.californium:scandium:2.7.3 > 2022-09-14T07:34:24.8332906Z > +-org.eclipse.californium:californium-legal:2.7.3 > 2022-09-14T07:34:24.8333204Z and > 2022-09-14T07:34:24.8333592Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8334030Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8334476Z > +-org.eclipse.californium:element-connector-tcp-netty:2.7.2 > 2022-09-14T07:34:24.8334946Z > +-org.eclipse.californium:californium-legal:2.7.2 > 2022-09-14T07:34:24.8335189Z > 2022-09-14T07:34:24.8335402Z [WARNING] > 2022-09-14T07:34:24.8335890Z Dependency convergence error for > org.eclipse.californium:element-connector:2.7.2 paths to dependency are: > 2022-09-14T07:34:24.8336425Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8336868Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8337522Z > +-org.eclipse.californium:californium-core:2.7.2 > 2022-09-14T07:34:24.8337984Z > +-org.eclipse.californium:element-connector:2.7.2 > 2022-09-14T07:34:24.8338286Z and > 2022-09-14T07:34:24.8338680Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8339126Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8339605Z +-org.eclipse.californium:scandium:2.7.3 > 2022-09-14T07:34:24.8340053Z > +-org.eclipse.californium:element-connector:2.7.3 > 2022-09-14T07:34:24.8340338Z and > 2022-09-14T07:34:24.8340717Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8341155Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8341615Z > +-org.eclipse.californium:element-connector-tcp-netty:2.7.2 > 2022-09-14T07:34:24.8342089Z > +-org.eclipse.californium:element-connector:2.7.2 {code} > Correct solution should be to move californium:element-connector and > californium:californium-legal: to version 2.7.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-10173) Create a camel component for etcd v3
[ https://issues.apache.org/jira/browse/CAMEL-10173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17604023#comment-17604023 ] Claus Ibsen commented on CAMEL-10173: - camel-etc3 is only a aggregation repository, it miss the general component > Create a camel component for etcd v3 > > > Key: CAMEL-10173 > URL: https://issues.apache.org/jira/browse/CAMEL-10173 > Project: Camel > Issue Type: New Feature >Reporter: Luca Burgazzoli >Priority: Major > Fix For: 3.x > > > See https://github.com/coreos/jetcd -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-10173) Create a camel component for etcd v3
[ https://issues.apache.org/jira/browse/CAMEL-10173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17604015#comment-17604015 ] Nicolas Filotto commented on CAMEL-10173: - The status is unclear, it seems to be fixed. Indeed I see this ticket https://issues.apache.org/jira/browse/CAMEL-15469 that is more or less a duplicate and this component [https://github.com/apache/camel/tree/main/components/camel-etcd3.] Do I miss something? > Create a camel component for etcd v3 > > > Key: CAMEL-10173 > URL: https://issues.apache.org/jira/browse/CAMEL-10173 > Project: Camel > Issue Type: New Feature >Reporter: Luca Burgazzoli >Priority: Major > Fix For: 3.x > > > See https://github.com/coreos/jetcd -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-11252) camel-core : allow to retrieve components/endpoints/etc list with a predicate
[ https://issues.apache.org/jira/browse/CAMEL-11252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17603991#comment-17603991 ] Nicolas Filotto commented on CAMEL-11252: - Should be fixed by https://github.com/apache/camel/pull/8370 > camel-core : allow to retrieve components/endpoints/etc list with a predicate > - > > Key: CAMEL-11252 > URL: https://issues.apache.org/jira/browse/CAMEL-11252 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Luca Burgazzoli >Priority: Major > Fix For: 3.x > > > As today components/endpoints and so on can be retrieved/removed from the > camel context by id but it would be nice to have a more flexible way to > retrieve them like: > {code:java} > List components = context.getComponents(id, component -> { > return component instanceof IdAware; > }); > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18505) Camel-coap: Version conflict (californium-legal and element-connector)
[ https://issues.apache.org/jira/browse/CAMEL-18505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Ondrusek updated CAMEL-18505: -- Summary: Camel-coap: Version conflict (californium-legal and element-connector) (was: Camel-coap: Version conflict () > Camel-coap: Version conflict (californium-legal and element-connector) > -- > > Key: CAMEL-18505 > URL: https://issues.apache.org/jira/browse/CAMEL-18505 > Project: Camel > Issue Type: Bug > Components: camel-coap >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > > Recent update of Scandium to 2.7.3 created 2 version conflicts in camel-coap. > Build of camel-quarkus extension copa fails with: > {code:java} > Dependency convergence error for > org.eclipse.californium:californium-legal:2.7.2 paths to dependency are: > 2022-09-14T07:34:24.8326810Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8327409Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8327954Z > +-org.eclipse.californium:californium-core:2.7.2 > 2022-09-14T07:34:24.8328418Z > +-org.eclipse.californium:californium-legal:2.7.2 > 2022-09-14T07:34:24.8328734Z and > 2022-09-14T07:34:24.8329134Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8329585Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8330014Z > +-org.eclipse.californium:californium-core:2.7.2 > 2022-09-14T07:34:24.8330456Z > +-org.eclipse.californium:element-connector:2.7.2 > 2022-09-14T07:34:24.8330902Z > +-org.eclipse.californium:californium-legal:2.7.2 > 2022-09-14T07:34:24.8331209Z and > 2022-09-14T07:34:24.8331597Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8332051Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8332467Z +-org.eclipse.californium:scandium:2.7.3 > 2022-09-14T07:34:24.8332906Z > +-org.eclipse.californium:californium-legal:2.7.3 > 2022-09-14T07:34:24.8333204Z and > 2022-09-14T07:34:24.8333592Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8334030Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8334476Z > +-org.eclipse.californium:element-connector-tcp-netty:2.7.2 > 2022-09-14T07:34:24.8334946Z > +-org.eclipse.californium:californium-legal:2.7.2 > 2022-09-14T07:34:24.8335189Z > 2022-09-14T07:34:24.8335402Z [WARNING] > 2022-09-14T07:34:24.8335890Z Dependency convergence error for > org.eclipse.californium:element-connector:2.7.2 paths to dependency are: > 2022-09-14T07:34:24.8336425Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8336868Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8337522Z > +-org.eclipse.californium:californium-core:2.7.2 > 2022-09-14T07:34:24.8337984Z > +-org.eclipse.californium:element-connector:2.7.2 > 2022-09-14T07:34:24.8338286Z and > 2022-09-14T07:34:24.8338680Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8339126Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8339605Z +-org.eclipse.californium:scandium:2.7.3 > 2022-09-14T07:34:24.8340053Z > +-org.eclipse.californium:element-connector:2.7.3 > 2022-09-14T07:34:24.8340338Z and > 2022-09-14T07:34:24.8340717Z > +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT > 2022-09-14T07:34:24.8341155Z > +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 > 2022-09-14T07:34:24.8341615Z > +-org.eclipse.californium:element-connector-tcp-netty:2.7.2 > 2022-09-14T07:34:24.8342089Z > +-org.eclipse.californium:element-connector:2.7.2 {code} > Correct solution should be to move californium:element-connector and > californium:californium-legal: to version 2.7.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18505) Camel-coap: Version conflict (
Jiri Ondrusek created CAMEL-18505: - Summary: Camel-coap: Version conflict ( Key: CAMEL-18505 URL: https://issues.apache.org/jira/browse/CAMEL-18505 Project: Camel Issue Type: Bug Components: camel-coap Reporter: Jiri Ondrusek Assignee: Jiri Ondrusek Recent update of Scandium to 2.7.3 created 2 version conflicts in camel-coap. Build of camel-quarkus extension copa fails with: {code:java} Dependency convergence error for org.eclipse.californium:californium-legal:2.7.2 paths to dependency are: 2022-09-14T07:34:24.8326810Z +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT 2022-09-14T07:34:24.8327409Z +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 2022-09-14T07:34:24.8327954Z +-org.eclipse.californium:californium-core:2.7.2 2022-09-14T07:34:24.8328418Z +-org.eclipse.californium:californium-legal:2.7.2 2022-09-14T07:34:24.8328734Z and 2022-09-14T07:34:24.8329134Z +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT 2022-09-14T07:34:24.8329585Z +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 2022-09-14T07:34:24.8330014Z +-org.eclipse.californium:californium-core:2.7.2 2022-09-14T07:34:24.8330456Z +-org.eclipse.californium:element-connector:2.7.2 2022-09-14T07:34:24.8330902Z +-org.eclipse.californium:californium-legal:2.7.2 2022-09-14T07:34:24.8331209Z and 2022-09-14T07:34:24.8331597Z +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT 2022-09-14T07:34:24.8332051Z +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 2022-09-14T07:34:24.8332467Z +-org.eclipse.californium:scandium:2.7.3 2022-09-14T07:34:24.8332906Z +-org.eclipse.californium:californium-legal:2.7.3 2022-09-14T07:34:24.8333204Z and 2022-09-14T07:34:24.8333592Z +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT 2022-09-14T07:34:24.8334030Z +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 2022-09-14T07:34:24.8334476Z +-org.eclipse.californium:element-connector-tcp-netty:2.7.2 2022-09-14T07:34:24.8334946Z +-org.eclipse.californium:californium-legal:2.7.2 2022-09-14T07:34:24.8335189Z 2022-09-14T07:34:24.8335402Z [WARNING] 2022-09-14T07:34:24.8335890Z Dependency convergence error for org.eclipse.californium:element-connector:2.7.2 paths to dependency are: 2022-09-14T07:34:24.8336425Z +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT 2022-09-14T07:34:24.8336868Z +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 2022-09-14T07:34:24.8337522Z +-org.eclipse.californium:californium-core:2.7.2 2022-09-14T07:34:24.8337984Z +-org.eclipse.californium:element-connector:2.7.2 2022-09-14T07:34:24.8338286Z and 2022-09-14T07:34:24.8338680Z +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT 2022-09-14T07:34:24.8339126Z +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 2022-09-14T07:34:24.8339605Z +-org.eclipse.californium:scandium:2.7.3 2022-09-14T07:34:24.8340053Z +-org.eclipse.californium:element-connector:2.7.3 2022-09-14T07:34:24.8340338Z and 2022-09-14T07:34:24.8340717Z +-org.apache.camel.quarkus:camel-quarkus-coap:2.13.0-SNAPSHOT 2022-09-14T07:34:24.8341155Z +-org.apache.camel:camel-coap:3.19.0-20220913.111253-62 2022-09-14T07:34:24.8341615Z +-org.eclipse.californium:element-connector-tcp-netty:2.7.2 2022-09-14T07:34:24.8342089Z +-org.eclipse.californium:element-connector:2.7.2 {code} Correct solution should be to move californium:element-connector and californium:californium-legal: to version 2.7.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18499) camel-kubernetes - Upgrade to 6.x
[ https://issues.apache.org/jira/browse/CAMEL-18499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Netherton resolved CAMEL-18499. - Resolution: Fixed > camel-kubernetes - Upgrade to 6.x > - > > Key: CAMEL-18499 > URL: https://issues.apache.org/jira/browse/CAMEL-18499 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kubernetes >Reporter: Claus Ibsen >Assignee: James Netherton >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18481) Allow Mail Consumer to handle duplicate/empty attachment filenames
[ https://issues.apache.org/jira/browse/CAMEL-18481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18481: Issue Type: New Feature (was: Improvement) > Allow Mail Consumer to handle duplicate/empty attachment filenames > -- > > Key: CAMEL-18481 > URL: https://issues.apache.org/jira/browse/CAMEL-18481 > Project: Camel > Issue Type: New Feature > Components: camel-mail >Reporter: Manuel Shenavai >Priority: Minor > Fix For: 3.19.0 > > > The mail consumer is not able to process mail attachments that are empty or > if no filename is set. Its also not possible to get all attachments of a mail > if they have the same filename. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18481) Allow Mail Consumer to handle duplicate/empty attachment filenames
[ https://issues.apache.org/jira/browse/CAMEL-18481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18481: Affects Version/s: (was: 3.19.0) > Allow Mail Consumer to handle duplicate/empty attachment filenames > -- > > Key: CAMEL-18481 > URL: https://issues.apache.org/jira/browse/CAMEL-18481 > Project: Camel > Issue Type: Improvement > Components: camel-mail >Reporter: Manuel Shenavai >Priority: Minor > > The mail consumer is not able to process mail attachments that are empty or > if no filename is set. Its also not possible to get all attachments of a mail > if they have the same filename. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18481) Allow Mail Consumer to handle duplicate/empty attachment filenames
[ https://issues.apache.org/jira/browse/CAMEL-18481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18481: Fix Version/s: 3.19.0 > Allow Mail Consumer to handle duplicate/empty attachment filenames > -- > > Key: CAMEL-18481 > URL: https://issues.apache.org/jira/browse/CAMEL-18481 > Project: Camel > Issue Type: Improvement > Components: camel-mail >Reporter: Manuel Shenavai >Priority: Minor > Fix For: 3.19.0 > > > The mail consumer is not able to process mail attachments that are empty or > if no filename is set. Its also not possible to get all attachments of a mail > if they have the same filename. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18481) Allow Mail Consumer to handle duplicate/empty attachment filenames
[ https://issues.apache.org/jira/browse/CAMEL-18481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18481. - Resolution: Fixed > Allow Mail Consumer to handle duplicate/empty attachment filenames > -- > > Key: CAMEL-18481 > URL: https://issues.apache.org/jira/browse/CAMEL-18481 > Project: Camel > Issue Type: New Feature > Components: camel-mail >Reporter: Manuel Shenavai >Priority: Minor > Fix For: 3.19.0 > > > The mail consumer is not able to process mail attachments that are empty or > if no filename is set. Its also not possible to get all attachments of a mail > if they have the same filename. -- This message was sent by Atlassian Jira (v8.20.10#820010)