[jira] [Created] (CAMEL-16176) camel-kafka - Bug in header filter strategy regexp pattern
Claus Ibsen created CAMEL-16176: --- Summary: camel-kafka - Bug in header filter strategy regexp pattern Key: CAMEL-16176 URL: https://issues.apache.org/jira/browse/CAMEL-16176 Project: Camel Issue Type: Bug Components: camel-kafka Affects Versions: 3.7.2, 3.8.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.7.3, 3.9.0 Reported on twitter https://twitter.com/AlbanAuzeill/status/1359278148039368704 For this blog https://blog.sonarsource.com/regular-expressions-present-challenges And pointing to our code at https://github.com/apache/camel/blob/41e5be070279a77aec13b8aba7c387015b75bccc/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaHeaderFilterStrategy.java#L29 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15964) Create a Google Cloud Storage component
[ https://issues.apache.org/jira/browse/CAMEL-15964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17281929#comment-17281929 ] Luca Burgazzoli commented on CAMEL-15964: - We love contributions, go ahead ! > Create a Google Cloud Storage component > --- > > Key: CAMEL-15964 > URL: https://issues.apache.org/jira/browse/CAMEL-15964 > Project: Camel > Issue Type: New Feature >Reporter: Luca Burgazzoli >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15964) Create a Google Cloud Storage component
[ https://issues.apache.org/jira/browse/CAMEL-15964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated CAMEL-15964: Fix Version/s: 3.9.0 > Create a Google Cloud Storage component > --- > > Key: CAMEL-15964 > URL: https://issues.apache.org/jira/browse/CAMEL-15964 > Project: Camel > Issue Type: New Feature >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 3.9.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15964) Create a Google Cloud Storage component
[ https://issues.apache.org/jira/browse/CAMEL-15964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17281915#comment-17281915 ] Raffaele Marcello commented on CAMEL-15964: --- Hi, I would like to contribute developing this component. I already started to work on it locally and I am preparing a solution similar to the aws2-s3 component. I studied the Google storage component java api, I defined the the consumer and the provider and I am preparing the junit tests. Do you think I can work officially on it and give this contribute? > Create a Google Cloud Storage component > --- > > Key: CAMEL-15964 > URL: https://issues.apache.org/jira/browse/CAMEL-15964 > Project: Camel > Issue Type: New Feature >Reporter: Luca Burgazzoli >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15635) Some Kudu tests are failing in JDK >= 12 builds
[ https://issues.apache.org/jira/browse/CAMEL-15635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-15635. Resolution: Fixed > Some Kudu tests are failing in JDK >= 12 builds > --- > > Key: CAMEL-15635 > URL: https://issues.apache.org/jira/browse/CAMEL-15635 > Project: Camel > Issue Type: Test > Components: camel-kudu >Affects Versions: 3.6.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.9.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-16084) salesforce: Out of order execution
[ https://issues.apache.org/jira/browse/CAMEL-16084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17281907#comment-17281907 ] Jeremy Ross edited comment on CAMEL-16084 at 2/9/21, 5:30 PM: -- [~davsclaus] My feeling is this is problematic behavior, and requires a workaround that requires users to deal with threading issues when they really shouldn't have to. But if you don't think there's an issue here, I'll close this. was (Author: jeremyross): [~davsclaus] My feeling is this is problematic behavior, and requires a workaround that requires users to deal with threading issues when they really shouldn't have to. But if you don't think there's any issue here, I'll close this. > salesforce: Out of order execution > -- > > Key: CAMEL-16084 > URL: https://issues.apache.org/jira/browse/CAMEL-16084 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 3.7.1 >Reporter: Jeremy Ross >Assignee: Jeremy Ross >Priority: Major > Attachments: wiretap-results.txt > > > When using a salesforce operation after an aggregator, control seems to > return to the aggregate caller immediately instead of proceeding with > processors downstream from the salesforce operation. This is the behavior I'd > expect if using the aggregator with parallelProcessing. > I believe this is longstanding behavior, however with the removal of the > `synchronous` option from the salesforce component (CAMEL-14138), we've > removed a workaround to this issue. > I'm seeing the same behavior with a salesforce operation via a wiretap with a > threadpool with poolsize, maxsize and queuesize of 1, which should > effectively behave in a synchronous manner. > Test case: https://gist.github.com/jeremyross/4d7d14a33452edf236faefda77ad3e3d -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16084) salesforce: Out of order execution
[ https://issues.apache.org/jira/browse/CAMEL-16084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17281907#comment-17281907 ] Jeremy Ross commented on CAMEL-16084: - [~davsclaus] My feeling is this is problematic behavior, and requires a workaround that requires users to deal with threading issues when they really shouldn't have to. But if you don't think there's any issue here, I'll close this. > salesforce: Out of order execution > -- > > Key: CAMEL-16084 > URL: https://issues.apache.org/jira/browse/CAMEL-16084 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 3.7.1 >Reporter: Jeremy Ross >Assignee: Jeremy Ross >Priority: Major > Attachments: wiretap-results.txt > > > When using a salesforce operation after an aggregator, control seems to > return to the aggregate caller immediately instead of proceeding with > processors downstream from the salesforce operation. This is the behavior I'd > expect if using the aggregator with parallelProcessing. > I believe this is longstanding behavior, however with the removal of the > `synchronous` option from the salesforce component (CAMEL-14138), we've > removed a workaround to this issue. > I'm seeing the same behavior with a salesforce operation via a wiretap with a > threadpool with poolsize, maxsize and queuesize of 1, which should > effectively behave in a synchronous manner. > Test case: https://gist.github.com/jeremyross/4d7d14a33452edf236faefda77ad3e3d -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16175) camel javascript routes loader
[ https://issues.apache.org/jira/browse/CAMEL-16175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-16175: Fix Version/s: 3.9.0 Description: With the pluggable routes loader in 3.8, we can port over more from camel-k. Lets port over JS And the others we can do too Kotlin, Groovy Summary: camel javascript routes loader (was: camel-) > camel javascript routes loader > -- > > Key: CAMEL-16175 > URL: https://issues.apache.org/jira/browse/CAMEL-16175 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.9.0 > > > With the pluggable routes loader in 3.8, we can port over more from camel-k. > Lets port over JS > And the others we can do too Kotlin, Groovy -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16175) camel-
Claus Ibsen created CAMEL-16175: --- Summary: camel- Key: CAMEL-16175 URL: https://issues.apache.org/jira/browse/CAMEL-16175 Project: Camel Issue Type: Improvement Reporter: Claus Ibsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16173) Camel Resilience4j Bulkhead seems to not limit concurrent requests
[ https://issues.apache.org/jira/browse/CAMEL-16173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-16173: Fix Version/s: 3.9.0 > Camel Resilience4j Bulkhead seems to not limit concurrent requests > -- > > Key: CAMEL-16173 > URL: https://issues.apache.org/jira/browse/CAMEL-16173 > Project: Camel > Issue Type: Bug >Affects Versions: 3.7.1, 3.7.2 >Reporter: Jesper Duelund Isaksen >Priority: Minor > Fix For: 3.9.0 > > > In an attempt to ensure proper error handling once a Camel route would reach > its configured Resilience4j Bulkhead limit, it was experienced that > regardless of Bulkhead configuration, the limit was never upheld. Seemingly > the Bulkhead has no effect within the circuit breaker. > The context in which the bug was experienced: > Spring Boot 2.4.2, Apache Camel 3.7.1 (reproducer tested using 3.7.2 as well). > A reproducer Maven project can be found here: [sys-jdi/camel-bulkhead-test: > Test of Resilience4J in Spring Boot application using Apache > Camel.|https://github.com/sys-jdi/camel-bulkhead-test] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16174) camel-zookeeper - Upgrade to latest 3.5.x
[ https://issues.apache.org/jira/browse/CAMEL-16174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17281867#comment-17281867 ] Claus Ibsen commented on CAMEL-16174: - Ah okay yeah there is a ZK 3.5.9 released > camel-zookeeper - Upgrade to latest 3.5.x > - > > Key: CAMEL-16174 > URL: https://issues.apache.org/jira/browse/CAMEL-16174 > Project: Camel > Issue Type: Improvement > Components: camel-zookeeper >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.9.0 > > > There is a newer 3.5.x version. > Check with kafka what ZK version it uses, whether we can jump to ZK 3.6.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16155) camel-zookeeper-master: add option to set a custom ManagedGroupFactory
[ https://issues.apache.org/jira/browse/CAMEL-16155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17281866#comment-17281866 ] Claus Ibsen commented on CAMEL-16155: - Created a ticket at quarkus-camel https://github.com/apache/camel-quarkus/issues/2221 So we can just register DefaultManagedGroupFactory in the registry so its autowired and then it avoids the osgi lookup > camel-zookeeper-master: add option to set a custom ManagedGroupFactory > -- > > Key: CAMEL-16155 > URL: https://issues.apache.org/jira/browse/CAMEL-16155 > Project: Camel > Issue Type: Improvement > Components: camel-zookeeper-master >Reporter: Luca Burgazzoli >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.9.0 > > > As today the ManagedGroupFactoryBuilder tries to detect if it is running on > an OSGi platform but we could add an option to explicit set the > ManagedGroupFactory so as example for quarkus, we can skip the check as OSGi > is definitively not in use. > See: https://github.com/apache/camel/pull/5032 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16155) camel-zookeeper-master: add option to set a custom ManagedGroupFactory
[ https://issues.apache.org/jira/browse/CAMEL-16155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-16155. - Resolution: Fixed > camel-zookeeper-master: add option to set a custom ManagedGroupFactory > -- > > Key: CAMEL-16155 > URL: https://issues.apache.org/jira/browse/CAMEL-16155 > Project: Camel > Issue Type: Improvement > Components: camel-zookeeper-master >Reporter: Luca Burgazzoli >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.9.0 > > > As today the ManagedGroupFactoryBuilder tries to detect if it is running on > an OSGi platform but we could add an option to explicit set the > ManagedGroupFactory so as example for quarkus, we can skip the check as OSGi > is definitively not in use. > See: https://github.com/apache/camel/pull/5032 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-16155) camel-zookeeper-master: add option to set a custom ManagedGroupFactory
[ https://issues.apache.org/jira/browse/CAMEL-16155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-16155: --- Assignee: Claus Ibsen > camel-zookeeper-master: add option to set a custom ManagedGroupFactory > -- > > Key: CAMEL-16155 > URL: https://issues.apache.org/jira/browse/CAMEL-16155 > Project: Camel > Issue Type: Improvement > Components: camel-zookeeper-master >Reporter: Luca Burgazzoli >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.9.0 > > > As today the ManagedGroupFactoryBuilder tries to detect if it is running on > an OSGi platform but we could add an option to explicit set the > ManagedGroupFactory so as example for quarkus, we can skip the check as OSGi > is definitively not in use. > See: https://github.com/apache/camel/pull/5032 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16174) camel-zookeeper - Upgrade to latest 3.5.x
[ https://issues.apache.org/jira/browse/CAMEL-16174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17281853#comment-17281853 ] Andrea Cosentino commented on CAMEL-16174: -- Kafka 2.7.0 uses Zookeeper 3.5.8 > camel-zookeeper - Upgrade to latest 3.5.x > - > > Key: CAMEL-16174 > URL: https://issues.apache.org/jira/browse/CAMEL-16174 > Project: Camel > Issue Type: Improvement > Components: camel-zookeeper >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.9.0 > > > There is a newer 3.5.x version. > Check with kafka what ZK version it uses, whether we can jump to ZK 3.6.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16174) camel-zookeeper - Upgrade to latest 3.5.x
Claus Ibsen created CAMEL-16174: --- Summary: camel-zookeeper - Upgrade to latest 3.5.x Key: CAMEL-16174 URL: https://issues.apache.org/jira/browse/CAMEL-16174 Project: Camel Issue Type: Improvement Components: camel-zookeeper Reporter: Claus Ibsen Fix For: 3.9.0 There is a newer 3.5.x version. Check with kafka what ZK version it uses, whether we can jump to ZK 3.6.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16173) Camel Resilience4j Bulkhead seems to not limit concurrent requests
Jesper Duelund Isaksen created CAMEL-16173: -- Summary: Camel Resilience4j Bulkhead seems to not limit concurrent requests Key: CAMEL-16173 URL: https://issues.apache.org/jira/browse/CAMEL-16173 Project: Camel Issue Type: Bug Affects Versions: 3.7.2, 3.7.1 Reporter: Jesper Duelund Isaksen In an attempt to ensure proper error handling once a Camel route would reach its configured Resilience4j Bulkhead limit, it was experienced that regardless of Bulkhead configuration, the limit was never upheld. Seemingly the Bulkhead has no effect within the circuit breaker. The context in which the bug was experienced: Spring Boot 2.4.2, Apache Camel 3.7.1 (reproducer tested using 3.7.2 as well). A reproducer Maven project can be found here: [sys-jdi/camel-bulkhead-test: Test of Resilience4J in Spring Boot application using Apache Camel.|https://github.com/sys-jdi/camel-bulkhead-test] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15635) Some Kudu tests are failing in JDK >= 12 builds
[ https://issues.apache.org/jira/browse/CAMEL-15635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-15635: Fix Version/s: 3.9.0 > Some Kudu tests are failing in JDK >= 12 builds > --- > > Key: CAMEL-15635 > URL: https://issues.apache.org/jira/browse/CAMEL-15635 > Project: Camel > Issue Type: Test > Components: camel-kudu >Affects Versions: 3.6.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.9.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16172) Upgrade to version 0.15.0 of OpenTelemetry
[ https://issues.apache.org/jira/browse/CAMEL-16172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-16172: Fix Version/s: 3.9.0 > Upgrade to version 0.15.0 of OpenTelemetry > -- > > Key: CAMEL-16172 > URL: https://issues.apache.org/jira/browse/CAMEL-16172 > Project: Camel > Issue Type: Improvement > Components: camel-opentelemetry >Affects Versions: 3.7.2, 3.8.0 >Reporter: Thomas Heggelund >Priority: Minor > Fix For: 3.9.0 > > > Camel-OpenTelemetry should be upgraded to version 0.15 of the OpenTelemetry > libraries. > There are some breaking changes that require codechange in the component -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16153) camel-report-maven-plugin: overallCoverageThreshold
[ https://issues.apache.org/jira/browse/CAMEL-16153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-16153: Fix Version/s: (was: 3.8.0) 3.9.0 > camel-report-maven-plugin: overallCoverageThreshold > --- > > Key: CAMEL-16153 > URL: https://issues.apache.org/jira/browse/CAMEL-16153 > Project: Camel > Issue Type: New Feature > Components: tooling >Reporter: Benjamin >Priority: Minor > Fix For: 3.9.0 > > > The camel-report-maven-plugin reports the coverage of each route > individually. When failOnError is activated, the coverageThreshold will > therefore apply on a per route basis. Projects may, however, have many > smaller helper routes that don't necessarily need to be tested. In this case, > an overall coverage threshold across all routes in the project should be > available. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16172) Upgrade to version 0.15.0 of OpenTelemetry
Thomas Heggelund created CAMEL-16172: Summary: Upgrade to version 0.15.0 of OpenTelemetry Key: CAMEL-16172 URL: https://issues.apache.org/jira/browse/CAMEL-16172 Project: Camel Issue Type: Improvement Components: camel-opentelemetry Affects Versions: 3.7.2, 3.8.0 Reporter: Thomas Heggelund Camel-OpenTelemetry should be upgraded to version 0.15 of the OpenTelemetry libraries. There are some breaking changes that require codechange in the component -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16171) Add uri-endpoint-override options to all AWS2 components
[
https://issues.apache.org/jira/browse/CAMEL-16171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-16171:
-
Fix Version/s: 3.9.0
> Add uri-endpoint-override options to all AWS2 components
>
>
> Key: CAMEL-16171
> URL: https://issues.apache.org/jira/browse/CAMEL-16171
> Project: Camel
> Issue Type: Task
> Components: camel-aws2
>Reporter: Peter Palaga
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.9.0
>
>
> As agreed in https://github.com/apache/camel-quarkus/pull/2217 we'd like to
> add {{uri-endpoint-override}} and {{override-endpoint}} options to all AWS2
> components not having it yet.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-16171) Add uri-endpoint-override options to all AWS2 components
Peter Palaga created CAMEL-16171:
Summary: Add uri-endpoint-override options to all AWS2 components
Key: CAMEL-16171
URL: https://issues.apache.org/jira/browse/CAMEL-16171
Project: Camel
Issue Type: Task
Components: camel-aws2
Reporter: Peter Palaga
Assignee: Andrea Cosentino
As agreed in https://github.com/apache/camel-quarkus/pull/2217 we'd like to add
{{uri-endpoint-override}} and {{override-endpoint}} options to all AWS2
components not having it yet.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-16141) Investigate failing mina tests on JDK >= 11
[ https://issues.apache.org/jira/browse/CAMEL-16141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-16141: Issue Type: Test (was: Task) > Investigate failing mina tests on JDK >= 11 > --- > > Key: CAMEL-16141 > URL: https://issues.apache.org/jira/browse/CAMEL-16141 > Project: Camel > Issue Type: Test >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.9.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16141) Investigate failing mina tests on JDK >= 11
[ https://issues.apache.org/jira/browse/CAMEL-16141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-16141: Fix Version/s: 3.9.0 > Investigate failing mina tests on JDK >= 11 > --- > > Key: CAMEL-16141 > URL: https://issues.apache.org/jira/browse/CAMEL-16141 > Project: Camel > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.9.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16153) camel-report-maven-plugin: overallCoverageThreshold
[ https://issues.apache.org/jira/browse/CAMEL-16153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-16153. - Fix Version/s: (was: 3.9.0) 3.8.0 Resolution: Fixed > camel-report-maven-plugin: overallCoverageThreshold > --- > > Key: CAMEL-16153 > URL: https://issues.apache.org/jira/browse/CAMEL-16153 > Project: Camel > Issue Type: New Feature > Components: tooling >Reporter: Benjamin >Priority: Minor > Fix For: 3.8.0 > > > The camel-report-maven-plugin reports the coverage of each route > individually. When failOnError is activated, the coverageThreshold will > therefore apply on a per route basis. Projects may, however, have many > smaller helper routes that don't necessarily need to be tested. In this case, > an overall coverage threshold across all routes in the project should be > available. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16153) camel-report-maven-plugin: overallCoverageThreshold
[ https://issues.apache.org/jira/browse/CAMEL-16153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17281707#comment-17281707 ] Benjamin commented on CAMEL-16153: -- Pull request opened https://github.com/apache/camel/pull/5057 > camel-report-maven-plugin: overallCoverageThreshold > --- > > Key: CAMEL-16153 > URL: https://issues.apache.org/jira/browse/CAMEL-16153 > Project: Camel > Issue Type: New Feature > Components: tooling >Reporter: Benjamin >Priority: Minor > Fix For: 3.9.0 > > > The camel-report-maven-plugin reports the coverage of each route > individually. When failOnError is activated, the coverageThreshold will > therefore apply on a per route basis. Projects may, however, have many > smaller helper routes that don't necessarily need to be tested. In this case, > an overall coverage threshold across all routes in the project should be > available. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16168) camel-oaipmh: Replace the JettyTestServer with wiremock
[ https://issues.apache.org/jira/browse/CAMEL-16168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-16168. Resolution: Fixed > camel-oaipmh: Replace the JettyTestServer with wiremock > --- > > Key: CAMEL-16168 > URL: https://issues.apache.org/jira/browse/CAMEL-16168 > Project: Camel > Issue Type: New Feature >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.8.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16168) camel-oaipmh: Replace the JettyTestServer with wiremock
[ https://issues.apache.org/jira/browse/CAMEL-16168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-16168: --- Fix Version/s: 3.8.0 > camel-oaipmh: Replace the JettyTestServer with wiremock > --- > > Key: CAMEL-16168 > URL: https://issues.apache.org/jira/browse/CAMEL-16168 > Project: Camel > Issue Type: New Feature >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.8.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16153) camel-report-maven-plugin: overallCoverageThreshold
[ https://issues.apache.org/jira/browse/CAMEL-16153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17281632#comment-17281632 ] Benjamin commented on CAMEL-16153: -- Starting to work on it today > camel-report-maven-plugin: overallCoverageThreshold > --- > > Key: CAMEL-16153 > URL: https://issues.apache.org/jira/browse/CAMEL-16153 > Project: Camel > Issue Type: New Feature > Components: tooling >Reporter: Benjamin >Priority: Minor > Fix For: 3.9.0 > > > The camel-report-maven-plugin reports the coverage of each route > individually. When failOnError is activated, the coverageThreshold will > therefore apply on a per route basis. Projects may, however, have many > smaller helper routes that don't necessarily need to be tested. In this case, > an overall coverage threshold across all routes in the project should be > available. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16138) Allow KafkaClientFactory to be used without explicit broker URLs
[ https://issues.apache.org/jira/browse/CAMEL-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17281622#comment-17281622 ] Claus Ibsen commented on CAMEL-16138: - Implemented this also for camel-vertx-kafka, and the client factory is autowired so its easier to plugin a custom impl > Allow KafkaClientFactory to be used without explicit broker URLs > > > Key: CAMEL-16138 > URL: https://issues.apache.org/jira/browse/CAMEL-16138 > Project: Camel > Issue Type: Improvement > Components: camel-kafka >Reporter: Nicola Ferraro >Assignee: John Poth >Priority: Major > Fix For: 3.8.0 > > > CAMEL-16071 has added support for KafkaClientFactory (thanks to > [~javierholguera]). It allows plugging a different implementation of the > Kafka Producer/Consumer, but the component still requires setting the > "brokers" configuration property in the component/endpoint, otherwise an > IllegalArgumentException is thrown. > > This prevents users and platforms to plug implementations of the Kafka > Producers/Consumers with fully externalized configuration (e.g. in > Camel-Quarkus we may be able in the near future to plug configuration > injected into files via Kubernetes service-binding). > > I think the check on the presence of the "brokers" property should be moved > into the default factory. > > cc: [~jpoth] -- This message was sent by Atlassian Jira (v8.3.4#803005)
