[jira] [Commented] (CAMEL-19356) Support SSL/TLS as source properties through 3rd parties services
[ https://issues.apache.org/jira/browse/CAMEL-19356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722991#comment-17722991 ] Claus Ibsen commented on CAMEL-19356: - Spring Boot 3.1 and unified SSL configuration https://docs.spring.io/spring-boot/docs/current-SNAPSHOT/reference/htmlsingle/#features.ssl > Support SSL/TLS as source properties through 3rd parties services > - > > Key: CAMEL-19356 > URL: https://issues.apache.org/jira/browse/CAMEL-19356 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Priority: Major > > Like we did for normal secret we could retrieve the needed bits for SSL/TLS. > For the properties we should re-use what we have for aws, gcp, azure and > hashicorp -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19354) camel-mybatis - Autowired sql connection factory
[ https://issues.apache.org/jira/browse/CAMEL-19354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19354. - Fix Version/s: 4.0-RC1 4.0 Resolution: Fixed > camel-mybatis - Autowired sql connection factory > > > Key: CAMEL-19354 > URL: https://issues.apache.org/jira/browse/CAMEL-19354 > Project: Camel > Issue Type: Improvement > Components: camel-mybatis >Reporter: Claus Ibsen >Assignee: Federico Mariani >Priority: Minor > Fix For: 4.0-RC1, 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19352) Improve camel-mybatis documentation
[ https://issues.apache.org/jira/browse/CAMEL-19352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19352. - Resolution: Fixed > Improve camel-mybatis documentation > --- > > Key: CAMEL-19352 > URL: https://issues.apache.org/jira/browse/CAMEL-19352 > Project: Camel > Issue Type: Improvement > Components: camel-mybatis, camel-spring-boot >Affects Versions: 3.20.4, 4.0-M3 >Reporter: Federico Mariani >Assignee: Federico Mariani >Priority: Major > Fix For: 3.20.5, 3.21.0, 4.0-RC1, 4.0 > > > * Add a doc paragraph about the integration between _camel-mybatis-starter_ > and _mybatis-spring-boot-starter_ > * _camel-mybatis-starter_ documentation properties are wrong, _mybatis-bean_ > is used instead of _mybatis_ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19281) Aws2- healthchecks not closing resources for awsClient
[ https://issues.apache.org/jira/browse/CAMEL-19281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19281: Fix Version/s: 3.20.5 (was: 3.20.4) > Aws2- healthchecks not closing resources for awsClient > -- > > Key: CAMEL-19281 > URL: https://issues.apache.org/jira/browse/CAMEL-19281 > Project: Camel > Issue Type: Bug > Components: camel-aws >Affects Versions: 3.19.0, 4.0-M2 >Reporter: Artem >Assignee: Rhuan Rocha >Priority: Major > Fix For: 3.20.5, 3.21.0, 4.0-RC1, 4.0 > > > As AWS2S3ConsumerHealthCheck and Sqs2ConsumerHealthCheck working with > SqsClient and S3Client, which extends AutoCloseble , meaning those have to be > properly handled in terms of closing resources, we noticed that in our > services invoking aws health checks leads to connection memory leak of > *org.apache.http.impl.conn.PoolingHttpClientConnectionManager* , pls take a > look -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19281) Aws2- healthchecks not closing resources for awsClient
[ https://issues.apache.org/jira/browse/CAMEL-19281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19281. - Resolution: Fixed > Aws2- healthchecks not closing resources for awsClient > -- > > Key: CAMEL-19281 > URL: https://issues.apache.org/jira/browse/CAMEL-19281 > Project: Camel > Issue Type: Bug > Components: camel-aws >Affects Versions: 3.19.0, 4.0-M2 >Reporter: Artem >Assignee: Rhuan Rocha >Priority: Major > Fix For: 3.21.0, 4.0-RC1, 4.0, 3.20.4 > > > As AWS2S3ConsumerHealthCheck and Sqs2ConsumerHealthCheck working with > SqsClient and S3Client, which extends AutoCloseble , meaning those have to be > properly handled in terms of closing resources, we noticed that in our > services invoking aws health checks leads to connection memory leak of > *org.apache.http.impl.conn.PoolingHttpClientConnectionManager* , pls take a > look -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19281) Aws2- healthchecks not closing resources for awsClient
[ https://issues.apache.org/jira/browse/CAMEL-19281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19281: Fix Version/s: 4.0-RC1 (was: 4.0-M3) > Aws2- healthchecks not closing resources for awsClient > -- > > Key: CAMEL-19281 > URL: https://issues.apache.org/jira/browse/CAMEL-19281 > Project: Camel > Issue Type: Bug > Components: camel-aws >Affects Versions: 3.19.0, 4.0-M2 >Reporter: Artem >Assignee: Rhuan Rocha >Priority: Major > Fix For: 3.20.4, 3.21.0, 4.0-RC1, 4.0 > > > As AWS2S3ConsumerHealthCheck and Sqs2ConsumerHealthCheck working with > SqsClient and S3Client, which extends AutoCloseble , meaning those have to be > properly handled in terms of closing resources, we noticed that in our > services invoking aws health checks leads to connection memory leak of > *org.apache.http.impl.conn.PoolingHttpClientConnectionManager* , pls take a > look -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19350) camel-jpa: Output into header/property
[ https://issues.apache.org/jira/browse/CAMEL-19350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19350. - Resolution: Fixed > camel-jpa: Output into header/property > -- > > Key: CAMEL-19350 > URL: https://issues.apache.org/jira/browse/CAMEL-19350 > Project: Camel > Issue Type: Improvement > Components: camel-jpa >Reporter: Jacek Szymański >Priority: Minor > Fix For: 3.21.0, 4.0-RC1, 4.0 > > > Unlike camel-sql, camel-jpa does not allow the user to put the result > elsewhere than the message body; if this is needed the user must: preserve > the body, use the component, put the result in the desired destination, > restore the body. > This PR adds the possibility to put the result into a header or property > without destroying the message body. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19350) camel-jpa: Output into header/property
[ https://issues.apache.org/jira/browse/CAMEL-19350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722986#comment-17722986 ] Claus Ibsen commented on CAMEL-19350: - Thanks for the PRs > camel-jpa: Output into header/property > -- > > Key: CAMEL-19350 > URL: https://issues.apache.org/jira/browse/CAMEL-19350 > Project: Camel > Issue Type: Improvement > Components: camel-jpa >Reporter: Jacek Szymański >Priority: Minor > Fix For: 3.21.0, 4.0-RC1, 4.0 > > > Unlike camel-sql, camel-jpa does not allow the user to put the result > elsewhere than the message body; if this is needed the user must: preserve > the body, use the component, put the result in the desired destination, > restore the body. > This PR adds the possibility to put the result into a header or property > without destroying the message body. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (CAMEL-19281) Aws2- healthchecks not closing resources for awsClient
[ https://issues.apache.org/jira/browse/CAMEL-19281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rhuan Rocha reopened CAMEL-19281: - [~artemtraier], I'm not sure the health checker is generating the issue you have described. Could you attach a reproducer? Could you tell us the components used in your application? > Aws2- healthchecks not closing resources for awsClient > -- > > Key: CAMEL-19281 > URL: https://issues.apache.org/jira/browse/CAMEL-19281 > Project: Camel > Issue Type: Bug > Components: camel-aws >Affects Versions: 3.19.0, 4.0-M2 >Reporter: Artem >Assignee: Rhuan Rocha >Priority: Major > Fix For: 3.20.4, 3.21.0, 4.0-M3, 4.0 > > > As AWS2S3ConsumerHealthCheck and Sqs2ConsumerHealthCheck working with > SqsClient and S3Client, which extends AutoCloseble , meaning those have to be > properly handled in terms of closing resources, we noticed that in our > services invoking aws health checks leads to connection memory leak of > *org.apache.http.impl.conn.PoolingHttpClientConnectionManager* , pls take a > look -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19358) camel-kafka - Kafka consumer is still able to consume message with keepOpen as true in ThrottlingExceptionRoutePolicy
[ https://issues.apache.org/jira/browse/CAMEL-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianbo Ma updated CAMEL-19358: -- Description: We have circuit breaker implementation in routes, and it is using ThrottlingExceptionRoutePolicy. Previously we were using version 3.18.0, the Kakfa consumer is not able to consume messages when keepOpen is true. However there was an issue with version 3.18.0, which was that the consumer couldn't be resumed after we changed the keepOpen to false, could be an issue related to https://issues.apache.org/jira/browse/CAMEL-18688 . We tried version 3.18.3 and 3.20.0, both versions have the same issue, Kafka consumer is able to consume message even with keepOpen as true, while for the route with JMS consumer, there is no such issue. Thanks, Jianbo was: We have circuit breaker implementation into routes, and it is using Thanks, Jianbo > camel-kafka - Kafka consumer is still able to consume message with keepOpen > as true in ThrottlingExceptionRoutePolicy > - > > Key: CAMEL-19358 > URL: https://issues.apache.org/jira/browse/CAMEL-19358 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 3.18.3, 3.20.0 >Reporter: Jianbo Ma >Priority: Minor > > We have circuit breaker implementation in routes, and it is using > ThrottlingExceptionRoutePolicy. Previously we were using version 3.18.0, the > Kakfa consumer is not able to consume messages when keepOpen is true. However > there was an issue with version 3.18.0, which was that the consumer couldn't > be resumed after we changed the keepOpen to false, could be an issue related > to https://issues.apache.org/jira/browse/CAMEL-18688 . We tried version > 3.18.3 and 3.20.0, both versions have the same issue, Kafka consumer is able > to consume message even with keepOpen as true, while for the route with JMS > consumer, there is no such issue. > Thanks, > Jianbo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19358) camel-kafka - Kafka consumer is still able to consume message with keepOpen as true in ThrottlingExceptionRoutePolicy
[
https://issues.apache.org/jira/browse/CAMEL-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianbo Ma updated CAMEL-19358:
--
Description:
We have circuit breaker implementation into routes, and it is using
Thanks,
Jianbo
was:
Hi,
while attempting to add the circuit breaker pattern to a route (see also
CAMEL-18759), I tried to use {{ThrottlingExceptionRoutePolicy}} to suspend and
resume the route when a specific exception is thrown. I noticed that regardless
of the {{breakOnFirstError}} setting, the message causing the circuit to be
opened is lost. If {{breakOnFirstError}} is {{true}}, logs are showing "Will
seek consumer to offset -1 and start polling again", but when the circuit is
closed the message is not consumed. I suspect that the consumer overwrites the
offset when it's suspended. If I switch to manual commits, everything works as
expected.
Reproducer here:
https://github.com/lorenzobenvenuti/camel-kafka-break-on-first-error-bug
Thanks,
lorenzo
> camel-kafka - Kafka consumer is still able to consume message with keepOpen
> as true in ThrottlingExceptionRoutePolicy
> -
>
> Key: CAMEL-19358
> URL: https://issues.apache.org/jira/browse/CAMEL-19358
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
>Affects Versions: 3.18.3, 3.20.0
>Reporter: Jianbo Ma
>Priority: Minor
>
> We have circuit breaker implementation into routes, and it is using
> Thanks,
> Jianbo
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19358) camel-kafka - Kafka consumer is still able to consume message with keepOpen as true in ThrottlingExceptionRoutePolicy
[
https://issues.apache.org/jira/browse/CAMEL-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianbo Ma updated CAMEL-19358:
--
Affects Version/s: 3.20.0
> camel-kafka - Kafka consumer is still able to consume message with keepOpen
> as true in ThrottlingExceptionRoutePolicy
> -
>
> Key: CAMEL-19358
> URL: https://issues.apache.org/jira/browse/CAMEL-19358
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
>Affects Versions: 3.18.3, 3.20.0
>Reporter: Jianbo Ma
>Priority: Minor
>
> Hi,
> while attempting to add the circuit breaker pattern to a route (see also
> CAMEL-18759), I tried to use {{ThrottlingExceptionRoutePolicy}} to suspend
> and resume the route when a specific exception is thrown. I noticed that
> regardless of the {{breakOnFirstError}} setting, the message causing the
> circuit to be opened is lost. If {{breakOnFirstError}} is {{true}}, logs are
> showing "Will seek consumer to offset -1 and start polling again", but when
> the circuit is closed the message is not consumed. I suspect that the
> consumer overwrites the offset when it's suspended. If I switch to manual
> commits, everything works as expected.
> Reproducer here:
> https://github.com/lorenzobenvenuti/camel-kafka-break-on-first-error-bug
> Thanks,
> lorenzo
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19358) camel-kafka - Kafka consumer is still able to consume message with keepOpen as true in ThrottlingExceptionRoutePolicy
[
https://issues.apache.org/jira/browse/CAMEL-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianbo Ma updated CAMEL-19358:
--
Fix Version/s: (was: 3.21.0)
> camel-kafka - Kafka consumer is still able to consume message with keepOpen
> as true in ThrottlingExceptionRoutePolicy
> -
>
> Key: CAMEL-19358
> URL: https://issues.apache.org/jira/browse/CAMEL-19358
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
>Affects Versions: 3.18.3
>Reporter: Jianbo Ma
>Priority: Minor
>
> Hi,
> while attempting to add the circuit breaker pattern to a route (see also
> CAMEL-18759), I tried to use {{ThrottlingExceptionRoutePolicy}} to suspend
> and resume the route when a specific exception is thrown. I noticed that
> regardless of the {{breakOnFirstError}} setting, the message causing the
> circuit to be opened is lost. If {{breakOnFirstError}} is {{true}}, logs are
> showing "Will seek consumer to offset -1 and start polling again", but when
> the circuit is closed the message is not consumed. I suspect that the
> consumer overwrites the offset when it's suspended. If I switch to manual
> commits, everything works as expected.
> Reproducer here:
> https://github.com/lorenzobenvenuti/camel-kafka-break-on-first-error-bug
> Thanks,
> lorenzo
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19358) camel-kafka - Kafka consumer is still able to consume message with keepOpen as true in ThrottlingExceptionRoutePolicy
Jianbo Ma created CAMEL-19358:
-
Summary: camel-kafka - Kafka consumer is still able to consume
message with keepOpen as true in ThrottlingExceptionRoutePolicy
Key: CAMEL-19358
URL: https://issues.apache.org/jira/browse/CAMEL-19358
Project: Camel
Issue Type: Bug
Components: camel-kafka
Affects Versions: 3.18.3
Reporter: Jianbo Ma
Fix For: 3.21.0
Hi,
while attempting to add the circuit breaker pattern to a route (see also
CAMEL-18759), I tried to use {{ThrottlingExceptionRoutePolicy}} to suspend and
resume the route when a specific exception is thrown. I noticed that regardless
of the {{breakOnFirstError}} setting, the message causing the circuit to be
opened is lost. If {{breakOnFirstError}} is {{true}}, logs are showing "Will
seek consumer to offset -1 and start polling again", but when the circuit is
closed the message is not consumed. I suspect that the consumer overwrites the
offset when it's suspended. If I switch to manual commits, everything works as
expected.
Reproducer here:
https://github.com/lorenzobenvenuti/camel-kafka-break-on-first-error-bug
Thanks,
lorenzo
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19357) camel-jbang - Use a vertx task for tasks to avoid blocking io thread
[ https://issues.apache.org/jira/browse/CAMEL-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19357: Fix Version/s: 3.20.5 > camel-jbang - Use a vertx task for tasks to avoid blocking io thread > > > Key: CAMEL-19357 > URL: https://issues.apache.org/jira/browse/CAMEL-19357 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.20.5, 3.21.0, 4.0-RC1, 4.0 > > > Otherwise if the task is too slow such as a slow download then you can see > WARN logs from vertx about ... Thread has been blocked for -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19357) camel-jbang - Use a vertx task for tasks to avoid blocking io thread
[ https://issues.apache.org/jira/browse/CAMEL-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19357. - Resolution: Fixed > camel-jbang - Use a vertx task for tasks to avoid blocking io thread > > > Key: CAMEL-19357 > URL: https://issues.apache.org/jira/browse/CAMEL-19357 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.21.0, 4.0-RC1, 4.0 > > > Otherwise if the task is too slow such as a slow download then you can see > WARN logs from vertx about ... Thread has been blocked for -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19357) camel-jbang - Use a vertx task for tasks to avoid blocking io thread
Claus Ibsen created CAMEL-19357: --- Summary: camel-jbang - Use a vertx task for tasks to avoid blocking io thread Key: CAMEL-19357 URL: https://issues.apache.org/jira/browse/CAMEL-19357 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.21.0, 4.0-RC1, 4.0 Otherwise if the task is too slow such as a slow download then you can see WARN logs from vertx about ... Thread has been blocked for -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19348) camel-tracing - Upgrade to 1.1.1
[ https://issues.apache.org/jira/browse/CAMEL-19348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722880#comment-17722880 ] Marcin Grzejszczak commented on CAMEL-19348: I fixed the build with this PR https://github.com/apache/camel/pull/10091 - what we fixed in Tracing broke sth in Camel but I applied a fix. I will need to one day figure out if how Camel actually plays around with scopes and parent-child relationship between spans is OK. > camel-tracing - Upgrade to 1.1.1 > > > Key: CAMEL-19348 > URL: https://issues.apache.org/jira/browse/CAMEL-19348 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-micrometer >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0-RC1, 4.0 > > > There are some test errors when upgrading in camel-observation. Also when > upgrading to a newer 1.0.x release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19356) Support SSL/TLS as source properties through 3rd parties services
Andrea Cosentino created CAMEL-19356: Summary: Support SSL/TLS as source properties through 3rd parties services Key: CAMEL-19356 URL: https://issues.apache.org/jira/browse/CAMEL-19356 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Like we did for normal secret we could retrieve the needed bits for SSL/TLS. For the properties we should re-use what we have for aws, gcp, azure and hashicorp -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19334) Upgrade spring-data-redis
[ https://issues.apache.org/jira/browse/CAMEL-19334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Mariani resolved CAMEL-19334. -- Resolution: Fixed > Upgrade spring-data-redis > - > > Key: CAMEL-19334 > URL: https://issues.apache.org/jira/browse/CAMEL-19334 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Federico Mariani >Assignee: Federico Mariani >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19313) camel-jbang - Provide a way to append Maven repository provided from command-line to the one provided in configuration
[
https://issues.apache.org/jira/browse/CAMEL-19313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-19313.
-
Fix Version/s: 3.20.5
3.21.0
4.0-RC1
4.0
Resolution: Fixed
> camel-jbang - Provide a way to append Maven repository provided from
> command-line to the one provided in configuration
> --
>
> Key: CAMEL-19313
> URL: https://issues.apache.org/jira/browse/CAMEL-19313
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Reporter: Aurélien Pupier
>Assignee: Federico Mariani
>Priority: Major
> Fix For: 3.20.5, 3.21.0, 4.0-RC1, 4.0
>
>
> it would be convenient to be able to have a Maven repository configured in
> configuration and to be able to provide another repos from command-line with
> --repos. Currently, it is always overriding (and needs to stay this way by
> default I think?).
> Currently:
> - jbang camel@apache/camel config set
> repos=https://maven.repository.redhat.com/ga
> - jbang camel@apache/camel run 'Test.java' --logging-level=info
> --repos=https://packages.atlassian.com/maven-external
> gives:
> {noformat}
> Running integration with the following configuration:
> --camel-version=3.18.3.redhat-00022
> --repos=https://packages.atlassian.com/maven-external
> {noformat}
> ideally, I when doing something like:
> - jbang camel@apache/camel config set
> repos=https://maven.repository.redhat.com/ga
> - jbang camel@apache/camel run 'Test.java' --logging-level=info
> --repos=$repos,https://packages.atlassian.com/maven-external
> should be giving:
> {noformat}
> Running integration with the following configuration:
> --camel-version=3.18.3.redhat-00022
>
> --repos=https://packages.atlassian.com/maven-external,https://maven.repository.redhat.com/ga
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19355) maven wrapper - Upgrade to 3.9.2
Claus Ibsen created CAMEL-19355: --- Summary: maven wrapper - Upgrade to 3.9.2 Key: CAMEL-19355 URL: https://issues.apache.org/jira/browse/CAMEL-19355 Project: Camel Issue Type: Task Components: build system Reporter: Claus Ibsen We are using 3.8.6, and there is a 3.8.8 release. But also a 3.9.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19354) camel-mybatis - Autowired sql connection factory
[ https://issues.apache.org/jira/browse/CAMEL-19354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-19354: --- Assignee: Federico Mariani > camel-mybatis - Autowired sql connection factory > > > Key: CAMEL-19354 > URL: https://issues.apache.org/jira/browse/CAMEL-19354 > Project: Camel > Issue Type: Improvement > Components: camel-mybatis >Reporter: Claus Ibsen >Assignee: Federico Mariani >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19354) camel-mybatis - Autowired sql connection factory
Claus Ibsen created CAMEL-19354: --- Summary: camel-mybatis - Autowired sql connection factory Key: CAMEL-19354 URL: https://issues.apache.org/jira/browse/CAMEL-19354 Project: Camel Issue Type: Improvement Components: camel-mybatis Reporter: Claus Ibsen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19353) Camel-Jbang reload exception
[
https://issues.apache.org/jira/browse/CAMEL-19353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722809#comment-17722809
]
Claus Ibsen commented on CAMEL-19353:
-
A potential fix has been pushed, Marat will retest when he has new CI builds
with SNAPSHOT jars
> Camel-Jbang reload exception
>
>
> Key: CAMEL-19353
> URL: https://issues.apache.org/jira/browse/CAMEL-19353
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Affects Versions: 3.21.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.21.0, 4.0-RC1, 4.0
>
>
> When I run the following route with camel-jbang:
> {code:java}
> - route:
> id: route-1791
> from:
> uri: kamelet:mqtt5-source
> id: from-fac9
> parameters:
> topic: data
> brokerUrl: '{{configmap:mqtt-server/broker-uri}}'
> username: '{{secret:mqtt-connection/username}}'
> password: '{{secret:mqtt-connection/password}}'
> clientId: client1
> steps:
> - log:
> message: ${body}
> id: log-cfb7
> {code}
> I have correct error message
> {code:java}
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route-1791: Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf...
> because of Failed to resolve endpoint:
> kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
> due to: Operation: [get] for kind: [ConfigMap] with name: [mqtt-server]
> in namespace: [karavan] failed.
> {code}
> When I run camel-jbang with empty --source-dir and then upload and run the
> same YAML I have an unexplainable message:
> {code:java}
> 2023-05-15 09:05:24.041 WARN 54202 --- [ntloop-thread-0]
> support.RouteOnDemandReloadStrategy : Error reloading routes due Failed to
> create route route-1791:
> Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf... because of
> Failed to resolve endpoint:
> kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
> due to: No httpclient implementations found on the context classloader,
> please ensure your classpath includes an implementation jar. This exception
> is ignored.
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route-1791: Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf...
> because of Failed to resolve endpoint:
> kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
> due to: No httpclient implementations found on the context classloader,
> please ensure your classpath includes an implementation jar
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19353) Camel-Jbang reload exception
[
https://issues.apache.org/jira/browse/CAMEL-19353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722797#comment-17722797
]
Claus Ibsen commented on CAMEL-19353:
-
public static HttpClient.Factory getHttpClientFactory() {
HttpClient.Factory factory = getFactory(
ServiceLoader.load(HttpClient.Factory.class,
Thread.currentThread().getContextClassLoader()));
if (factory == null) {
factory = getFactory(ServiceLoader.load(HttpClient.Factory.class,
HttpClientUtils.class.getClassLoader()));
if (factory == null) {
throw new KubernetesClientException(
"No httpclient implementations found on the context classloader,
please ensure your classpath includes an implementation jar");
}
}
LOGGER.debug("Using httpclient {} factory", factory.getClass().getName());
return factory;
}
> Camel-Jbang reload exception
>
>
> Key: CAMEL-19353
> URL: https://issues.apache.org/jira/browse/CAMEL-19353
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Affects Versions: 3.21.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.21.0, 4.0-RC1, 4.0
>
>
> When I run the following route with camel-jbang:
> {code:java}
> - route:
> id: route-1791
> from:
> uri: kamelet:mqtt5-source
> id: from-fac9
> parameters:
> topic: data
> brokerUrl: '{{configmap:mqtt-server/broker-uri}}'
> username: '{{secret:mqtt-connection/username}}'
> password: '{{secret:mqtt-connection/password}}'
> clientId: client1
> steps:
> - log:
> message: ${body}
> id: log-cfb7
> {code}
> I have correct error message
> {code:java}
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route-1791: Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf...
> because of Failed to resolve endpoint:
> kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
> due to: Operation: [get] for kind: [ConfigMap] with name: [mqtt-server]
> in namespace: [karavan] failed.
> {code}
> When I run camel-jbang with empty --source-dir and then upload and run the
> same YAML I have an unexplainable message:
> {code:java}
> 2023-05-15 09:05:24.041 WARN 54202 --- [ntloop-thread-0]
> support.RouteOnDemandReloadStrategy : Error reloading routes due Failed to
> create route route-1791:
> Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf... because of
> Failed to resolve endpoint:
> kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
> due to: No httpclient implementations found on the context classloader,
> please ensure your classpath includes an implementation jar. This exception
> is ignored.
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route-1791: Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf...
> because of Failed to resolve endpoint:
> kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
> due to: No httpclient implementations found on the context classloader,
> please ensure your classpath includes an implementation jar
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19353) Camel-Jbang reload exception
[
https://issues.apache.org/jira/browse/CAMEL-19353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722794#comment-17722794
]
Claus Ibsen commented on CAMEL-19353:
-
Okay I suspect its kubernetes-client as this works if you run outside k8s and
do not use configmap placeholders
> Camel-Jbang reload exception
>
>
> Key: CAMEL-19353
> URL: https://issues.apache.org/jira/browse/CAMEL-19353
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Affects Versions: 3.21.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.21.0, 4.0-RC1, 4.0
>
>
> When I run the following route with camel-jbang:
> {code:java}
> - route:
> id: route-1791
> from:
> uri: kamelet:mqtt5-source
> id: from-fac9
> parameters:
> topic: data
> brokerUrl: '{{configmap:mqtt-server/broker-uri}}'
> username: '{{secret:mqtt-connection/username}}'
> password: '{{secret:mqtt-connection/password}}'
> clientId: client1
> steps:
> - log:
> message: ${body}
> id: log-cfb7
> {code}
> I have correct error message
> {code:java}
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route-1791: Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf...
> because of Failed to resolve endpoint:
> kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
> due to: Operation: [get] for kind: [ConfigMap] with name: [mqtt-server]
> in namespace: [karavan] failed.
> {code}
> When I run camel-jbang with empty --source-dir and then upload and run the
> same YAML I have an unexplainable message:
> {code:java}
> 2023-05-15 09:05:24.041 WARN 54202 --- [ntloop-thread-0]
> support.RouteOnDemandReloadStrategy : Error reloading routes due Failed to
> create route route-1791:
> Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf... because of
> Failed to resolve endpoint:
> kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
> due to: No httpclient implementations found on the context classloader,
> please ensure your classpath includes an implementation jar. This exception
> is ignored.
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route-1791: Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf...
> because of Failed to resolve endpoint:
> kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
> due to: No httpclient implementations found on the context classloader,
> please ensure your classpath includes an implementation jar
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19353) Camel-Jbang reload exception
[
https://issues.apache.org/jira/browse/CAMEL-19353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19353:
Fix Version/s: 3.21.0
4.0-RC1
4.0
> Camel-Jbang reload exception
>
>
> Key: CAMEL-19353
> URL: https://issues.apache.org/jira/browse/CAMEL-19353
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Affects Versions: 3.21.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.21.0, 4.0-RC1, 4.0
>
>
> When I run the following route with camel-jbang:
> {code:java}
> - route:
> id: route-1791
> from:
> uri: kamelet:mqtt5-source
> id: from-fac9
> parameters:
> topic: data
> brokerUrl: '{{configmap:mqtt-server/broker-uri}}'
> username: '{{secret:mqtt-connection/username}}'
> password: '{{secret:mqtt-connection/password}}'
> clientId: client1
> steps:
> - log:
> message: ${body}
> id: log-cfb7
> {code}
> I have correct error message
> {code:java}
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route-1791: Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf...
> because of Failed to resolve endpoint:
> kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
> due to: Operation: [get] for kind: [ConfigMap] with name: [mqtt-server]
> in namespace: [karavan] failed.
> {code}
> When I run camel-jbang with empty --source-dir and then upload and run the
> same YAML I have an unexplainable message:
> {code:java}
> 2023-05-15 09:05:24.041 WARN 54202 --- [ntloop-thread-0]
> support.RouteOnDemandReloadStrategy : Error reloading routes due Failed to
> create route route-1791:
> Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf... because of
> Failed to resolve endpoint:
> kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
> due to: No httpclient implementations found on the context classloader,
> please ensure your classpath includes an implementation jar. This exception
> is ignored.
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route-1791: Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf...
> because of Failed to resolve endpoint:
> kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
> due to: No httpclient implementations found on the context classloader,
> please ensure your classpath includes an implementation jar
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-19353) Camel-Jbang reload exception
[
https://issues.apache.org/jira/browse/CAMEL-19353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-19353:
---
Assignee: Claus Ibsen
> Camel-Jbang reload exception
>
>
> Key: CAMEL-19353
> URL: https://issues.apache.org/jira/browse/CAMEL-19353
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Affects Versions: 3.21.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
>
> When I run the following route with camel-jbang:
> {code:java}
> - route:
> id: route-1791
> from:
> uri: kamelet:mqtt5-source
> id: from-fac9
> parameters:
> topic: data
> brokerUrl: '{{configmap:mqtt-server/broker-uri}}'
> username: '{{secret:mqtt-connection/username}}'
> password: '{{secret:mqtt-connection/password}}'
> clientId: client1
> steps:
> - log:
> message: ${body}
> id: log-cfb7
> {code}
> I have correct error message
> {code:java}
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route-1791: Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf...
> because of Failed to resolve endpoint:
> kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
> due to: Operation: [get] for kind: [ConfigMap] with name: [mqtt-server]
> in namespace: [karavan] failed.
> {code}
> When I run camel-jbang with empty --source-dir and then upload and run the
> same YAML I have an unexplainable message:
> {code:java}
> 2023-05-15 09:05:24.041 WARN 54202 --- [ntloop-thread-0]
> support.RouteOnDemandReloadStrategy : Error reloading routes due Failed to
> create route route-1791:
> Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf... because of
> Failed to resolve endpoint:
> kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
> due to: No httpclient implementations found on the context classloader,
> please ensure your classpath includes an implementation jar. This exception
> is ignored.
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route-1791: Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf...
> because of Failed to resolve endpoint:
> kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
> due to: No httpclient implementations found on the context classloader,
> please ensure your classpath includes an implementation jar
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19353) Camel-Jbang reload exception
Marat Gubaidullin created CAMEL-19353:
-
Summary: Camel-Jbang reload exception
Key: CAMEL-19353
URL: https://issues.apache.org/jira/browse/CAMEL-19353
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Affects Versions: 3.21.0
Reporter: Marat Gubaidullin
When I run the following route with camel-jbang:
{code:java}
- route:
id: route-1791
from:
uri: kamelet:mqtt5-source
id: from-fac9
parameters:
topic: data
brokerUrl: '{{configmap:mqtt-server/broker-uri}}'
username: '{{secret:mqtt-connection/username}}'
password: '{{secret:mqtt-connection/password}}'
clientId: client1
steps:
- log:
message: ${body}
id: log-cfb7
{code}
I have correct error message
{code:java}
org.apache.camel.FailedToCreateRouteException: Failed to create route
route-1791: Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf...
because of Failed to resolve endpoint:
kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
due to: Operation: [get] for kind: [ConfigMap] with name: [mqtt-server] in
namespace: [karavan] failed.
{code}
When I run camel-jbang with empty --source-dir and then upload and run the same
YAML I have an unexplainable message:
{code:java}
2023-05-15 09:05:24.041 WARN 54202 --- [ntloop-thread-0]
support.RouteOnDemandReloadStrategy : Error reloading routes due Failed to
create route route-1791:
Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf... because of
Failed to resolve endpoint:
kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
due to: No httpclient implementations found on the context classloader, please
ensure your classpath includes an implementation jar. This exception is ignored.
org.apache.camel.FailedToCreateRouteException: Failed to create route
route-1791: Route(route-1791)[From[kamelet:mqtt5-source?brokerUrl={{conf...
because of Failed to resolve endpoint:
kamelet:mqtt5-source?brokerUrl={{configmap:mqtt-server/broker-uri}}=xx=xx=data=xx
due to: No httpclient implementations found on the context classloader, please
ensure your classpath includes an implementation jar
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18599) Clearer syntax for the Choice EIP
[
https://issues.apache.org/jira/browse/CAMEL-18599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18599:
Fix Version/s: Future
(was: 4.0)
> Clearer syntax for the Choice EIP
> -
>
> Key: CAMEL-18599
> URL: https://issues.apache.org/jira/browse/CAMEL-18599
> Project: Camel
> Issue Type: Wish
> Components: came-core
>Reporter: Raymond
>Priority: Major
> Fix For: Future
>
>
> Currently, the Choice EIP has a somewhat confusing syntax. Example of a
> question on StackOverflow:
> [https://stackoverflow.com/questions/32382322/camel-end-vs-endchoice-not-the-usual-query]
> So basically:
> * {{.endChoice()}} --> to close a "when" predicate
> * {{.end()}} --> to close the entire "choice" block
> Though it's a bit drastic to change the syntax, but maybe a major version
> like 4.0 is suitable. For example
> * {{.endWhen()}} --> to close a "when" predicate
> * {{.endChoice()}} --> to close the entire "choice" block
> A little less drastic would be to change only the when.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18931) camel-websocket - Migrate to Jakarta EE for v4
[ https://issues.apache.org/jira/browse/CAMEL-18931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18931. - Resolution: Won't Do We have atmosphere and vertx for websocket. Adding a jetty based is a fair bit of work > camel-websocket - Migrate to Jakarta EE for v4 > -- > > Key: CAMEL-18931 > URL: https://issues.apache.org/jira/browse/CAMEL-18931 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0 > > > camel-websocket is an older jetty based component. It either needs to be > migrated or removed and deprecated in v3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18911) camel-optaplanner - Upgrade to 9.x in v4
[ https://issues.apache.org/jira/browse/CAMEL-18911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18911. - Resolution: Fixed > camel-optaplanner - Upgrade to 9.x in v4 > > > Key: CAMEL-18911 > URL: https://issues.apache.org/jira/browse/CAMEL-18911 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-optaplanner >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0 > > > We need optaplanner 9.0 to support JakartaEE and SB3/Q3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18958) camel-kubernetes - upgrade to 6.4.x
[ https://issues.apache.org/jira/browse/CAMEL-18958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18958. - Resolution: Fixed We have upgraded to 6.6.x > camel-kubernetes - upgrade to 6.4.x > --- > > Key: CAMEL-18958 > URL: https://issues.apache.org/jira/browse/CAMEL-18958 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-19348) camel-tracing - Upgrade to 1.1.1
[
https://issues.apache.org/jira/browse/CAMEL-19348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722748#comment-17722748
]
Claus Ibsen edited comment on CAMEL-19348 at 5/15/23 11:27 AM:
---
Okay but for the 1.0.x releases then if I upgrade
{code}
-1.10.6
-1.0.4
+1.10.7
+1.0.5
{code}
Then we have unit test errors in camel-observation and camel-micrometer
[~mgrzejszczak] ^^^
was (Author: davsclaus):
Okay but for the 1.0.x releases then if I upgrade
-1.10.6
-1.0.4
+1.10.7
+1.0.5
Then we have unit test errors in camel-observation and camel-micrometer
> camel-tracing - Upgrade to 1.1.1
>
>
> Key: CAMEL-19348
> URL: https://issues.apache.org/jira/browse/CAMEL-19348
> Project: Camel
> Issue Type: Dependency upgrade
> Components: camel-micrometer
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 4.0-RC1, 4.0
>
>
> There are some test errors when upgrading in camel-observation. Also when
> upgrading to a newer 1.0.x release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-19348) camel-tracing - Upgrade to 1.1.1
[
https://issues.apache.org/jira/browse/CAMEL-19348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722748#comment-17722748
]
Claus Ibsen edited comment on CAMEL-19348 at 5/15/23 11:27 AM:
---
Okay but for the 1.0.x releases then if I upgrade on main branch (Camel v4)
{code}
-1.10.6
-1.0.4
+1.10.7
+1.0.5
{code}
Then we have unit test errors in camel-observation and camel-micrometer
[~mgrzejszczak] ^^^
was (Author: davsclaus):
Okay but for the 1.0.x releases then if I upgrade
{code}
-1.10.6
-1.0.4
+1.10.7
+1.0.5
{code}
Then we have unit test errors in camel-observation and camel-micrometer
[~mgrzejszczak] ^^^
> camel-tracing - Upgrade to 1.1.1
>
>
> Key: CAMEL-19348
> URL: https://issues.apache.org/jira/browse/CAMEL-19348
> Project: Camel
> Issue Type: Dependency upgrade
> Components: camel-micrometer
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 4.0-RC1, 4.0
>
>
> There are some test errors when upgrading in camel-observation. Also when
> upgrading to a newer 1.0.x release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19348) camel-tracing - Upgrade to 1.1.1
[ https://issues.apache.org/jira/browse/CAMEL-19348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722748#comment-17722748 ] Claus Ibsen commented on CAMEL-19348: - Okay but for the 1.0.x releases then if I upgrade -1.10.6 -1.0.4 +1.10.7 +1.0.5 Then we have unit test errors in camel-observation and camel-micrometer > camel-tracing - Upgrade to 1.1.1 > > > Key: CAMEL-19348 > URL: https://issues.apache.org/jira/browse/CAMEL-19348 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-micrometer >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0-RC1, 4.0 > > > There are some test errors when upgrading in camel-observation. Also when > upgrading to a newer 1.0.x release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19348) camel-tracing - Upgrade to 1.1.1
[ https://issues.apache.org/jira/browse/CAMEL-19348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19348: Summary: camel-tracing - Upgrade to 1.1.1 (was: camel-tracing - Upgrade to 1.1.0) > camel-tracing - Upgrade to 1.1.1 > > > Key: CAMEL-19348 > URL: https://issues.apache.org/jira/browse/CAMEL-19348 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-micrometer >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0-RC1, 4.0 > > > There are some test errors when upgrading in camel-observation. Also when > upgrading to a newer 1.0.x release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19350) camel-jpa: Output into header/property
[ https://issues.apache.org/jira/browse/CAMEL-19350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19350: Fix Version/s: 3.21.0 4.0-RC1 4.0 > camel-jpa: Output into header/property > -- > > Key: CAMEL-19350 > URL: https://issues.apache.org/jira/browse/CAMEL-19350 > Project: Camel > Issue Type: Improvement > Components: camel-jpa >Reporter: Jacek Szymański >Priority: Minor > Fix For: 3.21.0, 4.0-RC1, 4.0 > > > Unlike camel-sql, camel-jpa does not allow the user to put the result > elsewhere than the message body; if this is needed the user must: preserve > the body, use the component, put the result in the desired destination, > restore the body. > This PR adds the possibility to put the result into a header or property > without destroying the message body. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19352) Improve camel-mybatis documentation
[ https://issues.apache.org/jira/browse/CAMEL-19352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19352: Fix Version/s: 3.20.5 3.21.0 4.0-RC1 4.0 > Improve camel-mybatis documentation > --- > > Key: CAMEL-19352 > URL: https://issues.apache.org/jira/browse/CAMEL-19352 > Project: Camel > Issue Type: Improvement > Components: camel-mybatis, camel-spring-boot >Affects Versions: 3.20.4, 4.0-M3 >Reporter: Federico Mariani >Assignee: Federico Mariani >Priority: Major > Fix For: 3.20.5, 3.21.0, 4.0-RC1, 4.0 > > > * Add a doc paragraph about the integration between _camel-mybatis-starter_ > and _mybatis-spring-boot-starter_ > * _camel-mybatis-starter_ documentation properties are wrong, _mybatis-bean_ > is used instead of _mybatis_ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19352) Improve camel-mybatis documentation
Federico Mariani created CAMEL-19352: Summary: Improve camel-mybatis documentation Key: CAMEL-19352 URL: https://issues.apache.org/jira/browse/CAMEL-19352 Project: Camel Issue Type: Improvement Components: camel-mybatis, camel-spring-boot Affects Versions: 4.0-M3, 3.20.4 Reporter: Federico Mariani Assignee: Federico Mariani * Add a doc paragraph about the integration between _camel-mybatis-starter_ and _mybatis-spring-boot-starter_ * _camel-mybatis-starter_ documentation properties are wrong, _mybatis-bean_ is used instead of _mybatis_ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19351) camel-jackson - Upgrade to 2.14.3
Claus Ibsen created CAMEL-19351: --- Summary: camel-jackson - Upgrade to 2.14.3 Key: CAMEL-19351 URL: https://issues.apache.org/jira/browse/CAMEL-19351 Project: Camel Issue Type: Dependency upgrade Components: camel-jackson Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.18.7, 3.20.5, 3.21.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19351) camel-jackson - Upgrade to 2.14.3
[ https://issues.apache.org/jira/browse/CAMEL-19351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19351. - Resolution: Fixed > camel-jackson - Upgrade to 2.14.3 > - > > Key: CAMEL-19351 > URL: https://issues.apache.org/jira/browse/CAMEL-19351 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.7, 3.20.5, 3.21.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19349) camel-core - Dev console for source to support camel-jbang source-dir
[ https://issues.apache.org/jira/browse/CAMEL-19349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19349. - Resolution: Fixed > camel-core - Dev console for source to support camel-jbang source-dir > - > > Key: CAMEL-19349 > URL: https://issues.apache.org/jira/browse/CAMEL-19349 > Project: Camel > Issue Type: New Feature > Components: camel-core, camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.21.0, 4.0-RC1, 4.0 > > > So /q/dev/source also can return all files loaded via jbang --source-dir > Currently its for routes only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-19349) camel-core - Dev console for source to support camel-jbang source-dir
[ https://issues.apache.org/jira/browse/CAMEL-19349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722462#comment-17722462 ] Claus Ibsen edited comment on CAMEL-19349 at 5/15/23 7:19 AM: -- TODO: list files *DONE* TODO: dump source (per file, pattern) *DONE* was (Author: davsclaus): TODO: list files *DONE* TODO: dump source (per file, pattern) > camel-core - Dev console for source to support camel-jbang source-dir > - > > Key: CAMEL-19349 > URL: https://issues.apache.org/jira/browse/CAMEL-19349 > Project: Camel > Issue Type: New Feature > Components: camel-core, camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.21.0, 4.0-RC1, 4.0 > > > So /q/dev/source also can return all files loaded via jbang --source-dir > Currently its for routes only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
