[jira] [Updated] (CAMEL-19004) XML IO DSL do not parse route configuration with XML namespace
[
https://issues.apache.org/jira/browse/CAMEL-19004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Dettinger updated CAMEL-19004:
---
Description:
XML IO DSL do not load {{routeConfiguration}} if it uses XML namespace like
this:
{code}
http://camel.apache.org/schema/spring;>
java.lang.Exception
true
{code}
A possible workaround is to explicitly remove the namespace, for instance like
below:
{code}
...
{code}
was:
XML IO DSL do not load {{routeConfiguration}} if it uses XML namespace like
this:
{code}
http://camel.apache.org/schema/spring;>
java.lang.Exception
true
{code}
> XML IO DSL do not parse route configuration with XML namespace
> --
>
> Key: CAMEL-19004
> URL: https://issues.apache.org/jira/browse/CAMEL-19004
> Project: Camel
> Issue Type: Bug
>Affects Versions: 3.18.3
>Reporter: Tomas Turek
>Priority: Minor
> Fix For: 3.18.6, 3.20.3, 3.21.0, 4.0-M2, 4.0
>
>
> XML IO DSL do not load {{routeConfiguration}} if it uses XML namespace like
> this:
> {code}
> http://camel.apache.org/schema/spring;>
>
> java.lang.Exception
> true
>
>
>
> {code}
> A possible workaround is to explicitly remove the namespace, for instance
> like below:
> {code}
>
> ...
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19006) XML IO DSL do not load templatedRoutes without XML namespace
[
https://issues.apache.org/jira/browse/CAMEL-19006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Dettinger updated CAMEL-19006:
---
Description:
XML IO DSL do not load templatedRoutes without XML namespace like this:
{code}
{code}
A possible workaround is to explicitly set the namespace, for instance like
below:
{code}
http://camel.apache.org/schema/spring;>
{code}
was:
XML IO DSL do not load templatedRoutes without XML namespace like this:
{code}
{code}
> XML IO DSL do not load templatedRoutes without XML namespace
>
>
> Key: CAMEL-19006
> URL: https://issues.apache.org/jira/browse/CAMEL-19006
> Project: Camel
> Issue Type: Bug
>Affects Versions: 3.18.3
>Reporter: Tomas Turek
>Priority: Minor
> Fix For: 3.18.6, 3.20.3, 3.21.0, 4.0-M2, 4.0
>
>
> XML IO DSL do not load templatedRoutes without XML namespace like this:
> {code}
>
>
>
>
>
>
> {code}
> A possible workaround is to explicitly set the namespace, for instance like
> below:
> {code}
> http://camel.apache.org/schema/spring;>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18751) camel-hbase: deprecate the component
[ https://issues.apache.org/jira/browse/CAMEL-18751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-18751. Resolution: Fixed > camel-hbase: deprecate the component > > > Key: CAMEL-18751 > URL: https://issues.apache.org/jira/browse/CAMEL-18751 > Project: Camel > Issue Type: Task > Components: camel-hbase >Affects Versions: 3.19.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18756) camel-spark: deprecate the component
Alex Dettinger created CAMEL-18756: -- Summary: camel-spark: deprecate the component Key: CAMEL-18756 URL: https://issues.apache.org/jira/browse/CAMEL-18756 Project: Camel Issue Type: Task Components: camel-hbase Affects Versions: 3.19.0 Reporter: Alex Dettinger Assignee: Alex Dettinger Fix For: 3.20.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18751) camel-hbase: deprecate the component
Alex Dettinger created CAMEL-18751: -- Summary: camel-hbase: deprecate the component Key: CAMEL-18751 URL: https://issues.apache.org/jira/browse/CAMEL-18751 Project: Camel Issue Type: Task Components: camel-hbase Affects Versions: 3.19.0 Reporter: Alex Dettinger Assignee: Alex Dettinger Fix For: 3.20.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18246) CVE-2022-26612: Upgrade hadoop-common >= 3.3.3
[ https://issues.apache.org/jira/browse/CAMEL-18246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563408#comment-17563408 ] Alex Dettinger commented on CAMEL-18246: Backported to 3.18.x: https://github.com/apache/camel/commit/792c12240aeeed7d658edaacf68b796e64a5b22f > CVE-2022-26612: Upgrade hadoop-common >= 3.3.3 > -- > > Key: CAMEL-18246 > URL: https://issues.apache.org/jira/browse/CAMEL-18246 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > It relates to > [CAMEL-QUARKUS-3763.|https://github.com/apache/camel-quarkus/issues/3763] > hdfs could be upgraded to 3.3.3, so that's ok. > However, hbase can't be updated to hadoop-common 2.10.2 as some tests fail. > Plus we are not sure whether 2.10.2 is really > [safer|https://issues.apache.org/jira/browse/HADOOP-18317]. If it's not > maintained actively, maybe deprecation would be needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18246) CVE-2022-26612: Upgrade hadoop-common >= 3.3.3
[ https://issues.apache.org/jira/browse/CAMEL-18246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-18246: --- Description: It relates to [CAMEL-QUARKUS-3763.|https://github.com/apache/camel-quarkus/issues/3763] hdfs could be upgraded to 3.3.3, so that's ok. However, hbase can't be updated to hadoop-common 2.10.2 as some tests fail. Plus we are not sure whether 2.10.2 is really [safer|https://issues.apache.org/jira/browse/HADOOP-18317]. If it's not maintained actively, maybe deprecation would be needed. was: It relates to [CAMEL-QUARKUS-3763.|https://github.com/apache/camel-quarkus/issues/3763] hdfs could be upgraded to 3.3.3, so that's ok. However, hbase can't be updated to hadoop-common 2.10.2 as some tests fail. Plus we are not sure whether 2.10.2 is really safer (HADOOP-18155). > CVE-2022-26612: Upgrade hadoop-common >= 3.3.3 > -- > > Key: CAMEL-18246 > URL: https://issues.apache.org/jira/browse/CAMEL-18246 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > It relates to > [CAMEL-QUARKUS-3763.|https://github.com/apache/camel-quarkus/issues/3763] > hdfs could be upgraded to 3.3.3, so that's ok. > However, hbase can't be updated to hadoop-common 2.10.2 as some tests fail. > Plus we are not sure whether 2.10.2 is really > [safer|https://issues.apache.org/jira/browse/HADOOP-18317]. If it's not > maintained actively, maybe deprecation would be needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18246) CVE-2022-26612: Upgrade hadoop-common >= 3.3.3
[ https://issues.apache.org/jira/browse/CAMEL-18246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-18246: --- Description: It relates to [CAMEL-QUARKUS-3763.|https://github.com/apache/camel-quarkus/issues/3763] hdfs could be upgraded to 3.3.3, so that's ok. However, hbase can't be updated to hadoop-common 2.10.2 as some tests fail. Plus we are not sure whether 2.10.2 is really safer (HADOOP-18155). was: It relates to [CAMEL-QUARKUS-3763|https://github.com/apache/camel-quarkus/issues/3763] where hbase and hdfs are affected by |CVE-2022-26612|https://nvd.nist.gov/vuln/detail/CVE-2022-26612]. According to HADOOP-18155, we need to upgrade to org.apache.hadoop:hadoop-common >= 2.10.2, 3.2.3, 3.3.3, 3.4.0. > CVE-2022-26612: Upgrade hadoop-common >= 3.3.3 > -- > > Key: CAMEL-18246 > URL: https://issues.apache.org/jira/browse/CAMEL-18246 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > It relates to > [CAMEL-QUARKUS-3763.|https://github.com/apache/camel-quarkus/issues/3763] > hdfs could be upgraded to 3.3.3, so that's ok. > However, hbase can't be updated to hadoop-common 2.10.2 as some tests fail. > Plus we are not sure whether 2.10.2 is really safer (HADOOP-18155). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18246) CVE-2022-26612: Upgrade hadoop-common >= 3.3.3
[ https://issues.apache.org/jira/browse/CAMEL-18246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17562436#comment-17562436 ] Alex Dettinger commented on CAMEL-18246: Backporting to 3.18.x: https://github.com/apache/camel/pull/7972 > CVE-2022-26612: Upgrade hadoop-common >= 3.3.3 > -- > > Key: CAMEL-18246 > URL: https://issues.apache.org/jira/browse/CAMEL-18246 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > It relates to > [CAMEL-QUARKUS-3763|https://github.com/apache/camel-quarkus/issues/3763] > where hbase and hdfs are affected by > |CVE-2022-26612|https://nvd.nist.gov/vuln/detail/CVE-2022-26612]. > According to HADOOP-18155, we need to upgrade to > org.apache.hadoop:hadoop-common >= 2.10.2, 3.2.3, 3.3.3, 3.4.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18246) CVE-2022-26612: Upgrade hadoop-common >= 3.3.3
[ https://issues.apache.org/jira/browse/CAMEL-18246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-18246: --- Description: It relates to [CAMEL-QUARKUS-3763|https://github.com/apache/camel-quarkus/issues/3763] where hbase and hdfs are affected by |CVE-2022-26612|https://nvd.nist.gov/vuln/detail/CVE-2022-26612]. According to HADOOP-18155, we need to upgrade to org.apache.hadoop:hadoop-common >= 2.10.2, 3.2.3, 3.3.3, 3.4.0. was: It relates to [CAMEL-QUAKRUS-3763|https://github.com/apache/camel-quarkus/issues/3763] where hbase and hdfs are affected by |CVE-2022-26612|https://nvd.nist.gov/vuln/detail/CVE-2022-26612]. According to HADOOP-18155, we need to upgrade to org.apache.hadoop:hadoop-common >= 2.10.2, 3.2.3, 3.3.3, 3.4.0. > CVE-2022-26612: Upgrade hadoop-common >= 3.3.3 > -- > > Key: CAMEL-18246 > URL: https://issues.apache.org/jira/browse/CAMEL-18246 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > It relates to > [CAMEL-QUARKUS-3763|https://github.com/apache/camel-quarkus/issues/3763] > where hbase and hdfs are affected by > |CVE-2022-26612|https://nvd.nist.gov/vuln/detail/CVE-2022-26612]. > According to HADOOP-18155, we need to upgrade to > org.apache.hadoop:hadoop-common >= 2.10.2, 3.2.3, 3.3.3, 3.4.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18246) CVE-2022-26612: Upgrade hadoop-common >= 3.3.3
[ https://issues.apache.org/jira/browse/CAMEL-18246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-18246: --- Summary: CVE-2022-26612: Upgrade hadoop-common >= 3.3.3 (was: CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3) > CVE-2022-26612: Upgrade hadoop-common >= 3.3.3 > -- > > Key: CAMEL-18246 > URL: https://issues.apache.org/jira/browse/CAMEL-18246 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > It relates to > [CAMEL-QUAKRUS-3763|https://github.com/apache/camel-quarkus/issues/3763] > where hbase and hdfs are affected by > |CVE-2022-26612|https://nvd.nist.gov/vuln/detail/CVE-2022-26612]. > According to HADOOP-18155, we need to upgrade to > org.apache.hadoop:hadoop-common >= 2.10.2, 3.2.3, 3.3.3, 3.4.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18246) CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3
[ https://issues.apache.org/jira/browse/CAMEL-18246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17562182#comment-17562182 ] Alex Dettinger commented on CAMEL-18246: So indeed, the update to hadoop-common 2.10.2 is breaking the hbase tests, plus we are not sure whether it's really safer (https://issues.apache.org/jira/browse/HADOOP-18317). However, it should be possible to upgrade the hadoop3-version to 3.3.3: https://github.com/apache/camel/pull/7970 > CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3 > -- > > Key: CAMEL-18246 > URL: https://issues.apache.org/jira/browse/CAMEL-18246 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > It relates to > [CAMEL-QUAKRUS-3763|https://github.com/apache/camel-quarkus/issues/3763] > where hbase and hdfs are affected by > |CVE-2022-26612|https://nvd.nist.gov/vuln/detail/CVE-2022-26612]. > According to HADOOP-18155, we need to upgrade to > org.apache.hadoop:hadoop-common >= 2.10.2, 3.2.3, 3.3.3, 3.4.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18246) CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3
[ https://issues.apache.org/jira/browse/CAMEL-18246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17561332#comment-17561332 ] Alex Dettinger commented on CAMEL-18246: Ok, we finally reverted everything as some itests were broken in CI. Let's retake this step by step after the release. > CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3 > -- > > Key: CAMEL-18246 > URL: https://issues.apache.org/jira/browse/CAMEL-18246 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.18.0 > > > It relates to > [CAMEL-QUAKRUS-3763|https://github.com/apache/camel-quarkus/issues/3763] > where hbase and hdfs are affected by > |CVE-2022-26612|https://nvd.nist.gov/vuln/detail/CVE-2022-26612]. > According to HADOOP-18155, we need to upgrade to > org.apache.hadoop:hadoop-common >= 2.10.2, 3.2.3, 3.3.3, 3.4.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18246) CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3
[ https://issues.apache.org/jira/browse/CAMEL-18246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17560896#comment-17560896 ] Alex Dettinger edited comment on CAMEL-18246 at 6/30/22 9:26 AM: - For hbase we tried to update the hadoop-common version to 3.2.3 in [https://github.com/apache/camel/pull/7940.] but it has broken some ci tests. was (Author: aldettinger): For hbase it was possible to update the hadoop-common version to 3.2.3 in [https://github.com/apache/camel/pull/7940.] > CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3 > -- > > Key: CAMEL-18246 > URL: https://issues.apache.org/jira/browse/CAMEL-18246 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.18.0 > > > It relates to > [CAMEL-QUAKRUS-3763|https://github.com/apache/camel-quarkus/issues/3763] > where hbase and hdfs are affected by > |CVE-2022-26612|https://nvd.nist.gov/vuln/detail/CVE-2022-26612]. > According to HADOOP-18155, we need to upgrade to > org.apache.hadoop:hadoop-common >= 2.10.2, 3.2.3, 3.3.3, 3.4.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18246) CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3
[ https://issues.apache.org/jira/browse/CAMEL-18246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17560896#comment-17560896 ] Alex Dettinger commented on CAMEL-18246: For hbase it was possible to update the hadoop-common version to 3.2.3 in [https://github.com/apache/camel/pull/7940.] > CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3 > -- > > Key: CAMEL-18246 > URL: https://issues.apache.org/jira/browse/CAMEL-18246 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.18.0 > > > It relates to > [CAMEL-QUAKRUS-3763|https://github.com/apache/camel-quarkus/issues/3763] > where hbase and hdfs are affected by > |CVE-2022-26612|https://nvd.nist.gov/vuln/detail/CVE-2022-26612]. > According to HADOOP-18155, we need to upgrade to > org.apache.hadoop:hadoop-common >= 2.10.2, 3.2.3, 3.3.3, 3.4.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18246) CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3
Title: Message Title Alex Dettinger commented on CAMEL-18246 Re: CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3 yep, I need to sort the dependency issue in the PR first: https://github.com/apache/camel/pull/7928. Let's see whether https://issues.apache.org/jira/browse/HADOOP-18317 could help. If the issue is really fixed, then let's see after if something could be done for camel-3.14.x branch. Add Comment This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)
[jira] [Updated] (CAMEL-18246) CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3
Title: Message Title Alex Dettinger updated an issue Camel / CAMEL-18246 CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3 Change By: Alex Dettinger It relates to [CAMEL-QUAKRUS-3763|https://github.com/apache/camel-quarkus/issues/3763] where hbase and hdfs are affected by|CVE-2022-26612|https://nvd.nist.gov/vuln/detail/CVE-2022-26612].According to HADOOP-18155, we need to upgrade to org.apache.hadoop:hadoop-common >= 2.10.2, 3.2.3, 3.3.3, 3.4.0. Add Comment This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)
[jira] [Updated] (CAMEL-18246) CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3
Title: Message Title Alex Dettinger updated an issue Camel / CAMEL-18246 CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3 Change By: Alex Dettinger It relates to [CAMEL-QUAKRUS-3763|https://github.com/apache/camel-quarkus/issues/3763] where hbase and hdfs are affected by Add Comment This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)
[jira] [Assigned] (CAMEL-18246) CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3
Title: Message Title Alex Dettinger assigned an issue to Alex Dettinger Camel / CAMEL-18246 CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3 Change By: Alex Dettinger Assignee: Alex Dettinger Add Comment This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)
[jira] [Created] (CAMEL-18246) CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3
Title: Message Title Alex Dettinger created an issue Camel / CAMEL-18246 CVE-2022-26612: Upgrade hadoop-common >= 2.10.2, 3.3.3 Issue Type: Task Assignee: Unassigned Created: 29/Jun/22 11:17 Priority: Major Reporter: Alex Dettinger Add Comment This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)
[jira] [Resolved] (CAMEL-17853) camel-zipfile: the case where the body is not a file is not tested
[ https://issues.apache.org/jira/browse/CAMEL-17853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-17853. Resolution: Fixed Actually, this case is already tested in AggregationStrategyWithFilenameHeaderTest.testSplitter(). > camel-zipfile: the case where the body is not a file is not tested > -- > > Key: CAMEL-17853 > URL: https://issues.apache.org/jira/browse/CAMEL-17853 > Project: Camel > Issue Type: Test > Components: camel-zipfile >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Trivial > Fix For: 3.17.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (CAMEL-17853) camel-zipfile: the case where the body is not a file is not tested
[ https://issues.apache.org/jira/browse/CAMEL-17853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger reassigned CAMEL-17853: -- Assignee: Alex Dettinger > camel-zipfile: the case where the body is not a file is not tested > -- > > Key: CAMEL-17853 > URL: https://issues.apache.org/jira/browse/CAMEL-17853 > Project: Camel > Issue Type: Test > Components: camel-zipfile >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Trivial > Fix For: 3.17.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-17853) camel-zipfile: the case where the body is not a file is not tested
[ https://issues.apache.org/jira/browse/CAMEL-17853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-17853: --- Fix Version/s: 3.17.0 (was: 3.x) > camel-zipfile: the case where the body is not a file is not tested > -- > > Key: CAMEL-17853 > URL: https://issues.apache.org/jira/browse/CAMEL-17853 > Project: Camel > Issue Type: Test > Components: camel-zipfile >Reporter: Alex Dettinger >Priority: Trivial > Fix For: 3.17.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-17853) zipfile: the case where the body is not a file is not tested
[ https://issues.apache.org/jira/browse/CAMEL-17853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17511930#comment-17511930 ] Alex Dettinger commented on CAMEL-17853: [~jirisimek98] Would you like to have a try ? > zipfile: the case where the body is not a file is not tested > > > Key: CAMEL-17853 > URL: https://issues.apache.org/jira/browse/CAMEL-17853 > Project: Camel > Issue Type: Test >Reporter: Alex Dettinger >Priority: Trivial > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17853) zipfile: the case where the body is not a file is not tested
Alex Dettinger created CAMEL-17853: -- Summary: zipfile: the case where the body is not a file is not tested Key: CAMEL-17853 URL: https://issues.apache.org/jira/browse/CAMEL-17853 Project: Camel Issue Type: Test Reporter: Alex Dettinger -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17178) doc: Fix some wrong links in documentation
[ https://issues.apache.org/jira/browse/CAMEL-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-17178. Resolution: Fixed > doc: Fix some wrong links in documentation > -- > > Key: CAMEL-17178 > URL: https://issues.apache.org/jira/browse/CAMEL-17178 > Project: Camel > Issue Type: Bug > Components: documentation >Affects Versions: 3.13.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.14.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17178) doc: Fix some wrong links in documentation
[ https://issues.apache.org/jira/browse/CAMEL-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-17178: --- Affects Version/s: 3.13.0 (was: 3.12.0) > doc: Fix some wrong links in documentation > -- > > Key: CAMEL-17178 > URL: https://issues.apache.org/jira/browse/CAMEL-17178 > Project: Camel > Issue Type: Bug > Components: documentation >Affects Versions: 3.13.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.14.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17178) doc: Fix some wrong links in documentation
[ https://issues.apache.org/jira/browse/CAMEL-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-17178: --- Fix Version/s: 3.14.0 (was: 3.13.0) > doc: Fix some wrong links in documentation > -- > > Key: CAMEL-17178 > URL: https://issues.apache.org/jira/browse/CAMEL-17178 > Project: Camel > Issue Type: Bug > Components: documentation >Affects Versions: 3.12.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.14.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17178) doc: Fix some wrong links in documentation
Alex Dettinger created CAMEL-17178: -- Summary: doc: Fix some wrong links in documentation Key: CAMEL-17178 URL: https://issues.apache.org/jira/browse/CAMEL-17178 Project: Camel Issue Type: Bug Components: documentation Affects Versions: 3.12.0 Reporter: Alex Dettinger Assignee: Alex Dettinger Fix For: 3.13.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17012) camel-aws2-lambda: ListAliases unduly return "Function Version must be specified to list aliases for a function"
[ https://issues.apache.org/jira/browse/CAMEL-17012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-17012. Resolution: Fixed Okay, this one can't be backported to 3.11.x without raising the localstack version. So, better keep the branch stable. > camel-aws2-lambda: ListAliases unduly return "Function Version must be > specified to list aliases for a function" > > > Key: CAMEL-17012 > URL: https://issues.apache.org/jira/browse/CAMEL-17012 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.12.0 >Reporter: Alex Dettinger >Priority: Minor > Fix For: 3.13.. > > > The listAliases operation unduly fails in aws lambda. > The underlying request is not built in the Lambda2Producer class and the > functionVersion parameter is unduly required. > From the doc > [https://docs.aws.amazon.com/lambda/latest/dg/API_ListAliases.html,] the > functionVersion should not be required. From the history I've been able to > grab, it seems it was never required in which case I guess it should be fine > to relax the constraint. > > A workaround is to use pojoRequest and define the request explicitly by hand. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-17012) camel-aws2-lambda: ListAliases unduly return "Function Version must be specified to list aliases for a function"
[ https://issues.apache.org/jira/browse/CAMEL-17012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17421432#comment-17421432 ] Alex Dettinger edited comment on CAMEL-17012 at 9/28/21, 2:42 PM: -- Okay, this one can't be backported to 3.11.x without raising the localstack version. So, better keep the 3.11.x branch stable. was (Author: aldettinger): Okay, this one can't be backported to 3.11.x without raising the localstack version. So, better keep the branch stable. > camel-aws2-lambda: ListAliases unduly return "Function Version must be > specified to list aliases for a function" > > > Key: CAMEL-17012 > URL: https://issues.apache.org/jira/browse/CAMEL-17012 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.12.0 >Reporter: Alex Dettinger >Priority: Minor > Fix For: 3.13.. > > > The listAliases operation unduly fails in aws lambda. > The underlying request is not built in the Lambda2Producer class and the > functionVersion parameter is unduly required. > From the doc > [https://docs.aws.amazon.com/lambda/latest/dg/API_ListAliases.html,] the > functionVersion should not be required. From the history I've been able to > grab, it seems it was never required in which case I guess it should be fine > to relax the constraint. > > A workaround is to use pojoRequest and define the request explicitly by hand. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-17012) camel-aws2-lambda: ListAliases unduly return "Function Version must be specified to list aliases for a function"
[ https://issues.apache.org/jira/browse/CAMEL-17012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-17012: --- Fix Version/s: (was: 3.11.3) > camel-aws2-lambda: ListAliases unduly return "Function Version must be > specified to list aliases for a function" > > > Key: CAMEL-17012 > URL: https://issues.apache.org/jira/browse/CAMEL-17012 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.12.0 >Reporter: Alex Dettinger >Priority: Minor > Fix For: 3.13.. > > > The listAliases operation unduly fails in aws lambda. > The underlying request is not built in the Lambda2Producer class and the > functionVersion parameter is unduly required. > From the doc > [https://docs.aws.amazon.com/lambda/latest/dg/API_ListAliases.html,] the > functionVersion should not be required. From the history I've been able to > grab, it seems it was never required in which case I guess it should be fine > to relax the constraint. > > A workaround is to use pojoRequest and define the request explicitly by hand. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-17012) camel-aws2-lambda: ListAliases unduly return "Function Version must be specified to list aliases for a function"
[ https://issues.apache.org/jira/browse/CAMEL-17012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-17012: --- Affects Version/s: (was: 3.11.2) > camel-aws2-lambda: ListAliases unduly return "Function Version must be > specified to list aliases for a function" > > > Key: CAMEL-17012 > URL: https://issues.apache.org/jira/browse/CAMEL-17012 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.12.0 >Reporter: Alex Dettinger >Priority: Minor > Fix For: 3.11.3, 3.13.. > > > The listAliases operation unduly fails in aws lambda. > The underlying request is not built in the Lambda2Producer class and the > functionVersion parameter is unduly required. > From the doc > [https://docs.aws.amazon.com/lambda/latest/dg/API_ListAliases.html,] the > functionVersion should not be required. From the history I've been able to > grab, it seems it was never required in which case I guess it should be fine > to relax the constraint. > > A workaround is to use pojoRequest and define the request explicitly by hand. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-17012) camel-aws2-lambda: ListAliases unduly return "Function Version must be specified to list aliases for a function"
[ https://issues.apache.org/jira/browse/CAMEL-17012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-17012: --- Affects Version/s: 3.11.2 > camel-aws2-lambda: ListAliases unduly return "Function Version must be > specified to list aliases for a function" > > > Key: CAMEL-17012 > URL: https://issues.apache.org/jira/browse/CAMEL-17012 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.11.2, 3.12.0 >Reporter: Alex Dettinger >Priority: Minor > Fix For: 3.11.3, 3.13.. > > > The listAliases operation unduly fails in aws lambda. > The underlying request is not built in the Lambda2Producer class and the > functionVersion parameter is unduly required. > From the doc > [https://docs.aws.amazon.com/lambda/latest/dg/API_ListAliases.html,] the > functionVersion should not be required. From the history I've been able to > grab, it seems it was never required in which case I guess it should be fine > to relax the constraint. > > A workaround is to use pojoRequest and define the request explicitly by hand. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-17012) camel-aws2-lambda: ListAliases unduly return "Function Version must be specified to list aliases for a function"
[ https://issues.apache.org/jira/browse/CAMEL-17012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-17012: --- Description: The listAliases operation unduly fails in aws lambda. The underlying request is not built in the Lambda2Producer class and the functionVersion parameter is unduly required. >From the doc >[https://docs.aws.amazon.com/lambda/latest/dg/API_ListAliases.html,] the >functionVersion should not be required. From the history I've been able to >grab, it seems it was never required in which case I guess it should be fine >to relax the constraint. A workaround is to use pojoRequest and define the request explicitly by hand. was: The listAliases operation unduly fails in aws lambda. The underlying request is not built and the functionVersion parameter is unduly required. >From the doc >[https://docs.aws.amazon.com/lambda/latest/dg/API_ListAliases.html,] the >functionVersion should not be required. From the history I've been able to >grab, it seems it was never required in which case I guess it should be fine >to relax the constraint. A workaround is to use pojoRequest and define the request explicitly by hand. > camel-aws2-lambda: ListAliases unduly return "Function Version must be > specified to list aliases for a function" > > > Key: CAMEL-17012 > URL: https://issues.apache.org/jira/browse/CAMEL-17012 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.12.0 >Reporter: Alex Dettinger >Priority: Minor > Fix For: 3.11.3, 3.13.. > > > The listAliases operation unduly fails in aws lambda. > The underlying request is not built in the Lambda2Producer class and the > functionVersion parameter is unduly required. > From the doc > [https://docs.aws.amazon.com/lambda/latest/dg/API_ListAliases.html,] the > functionVersion should not be required. From the history I've been able to > grab, it seems it was never required in which case I guess it should be fine > to relax the constraint. > > A workaround is to use pojoRequest and define the request explicitly by hand. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-17012) camel-aws2-lambda: ListAliases unduly return "Function Version must be specified to list aliases for a function"
[ https://issues.apache.org/jira/browse/CAMEL-17012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-17012: --- Description: The listAliases operation unduly fails in aws lambda. The underlying request is not built and the functionVersion parameter is unduly required. >From the doc >[https://docs.aws.amazon.com/lambda/latest/dg/API_ListAliases.html,] the >functionVersion should not be required. From the history I've been able to >grab, it seems it was never required in which case I guess it should be fine >to relax the constraint. A workaround is to use pojoRequest and define the request explicitly by hand. was: The listAliases operation unduly fails in aws lambda. The underlying request is not built and the functionVersion parameter is unduly required. >From the doc >[https://docs.aws.amazon.com/lambda/latest/dg/API_ListAliases.html,] the >functionVersion should not be required. From the history I've been able to >grab, it seems it was never required in which case I guess it should be fine >to relax the constraint. > camel-aws2-lambda: ListAliases unduly return "Function Version must be > specified to list aliases for a function" > > > Key: CAMEL-17012 > URL: https://issues.apache.org/jira/browse/CAMEL-17012 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.12.0 >Reporter: Alex Dettinger >Priority: Minor > Fix For: 3.11.3, 3.13.. > > > The listAliases operation unduly fails in aws lambda. > The underlying request is not built and the functionVersion parameter is > unduly required. > From the doc > [https://docs.aws.amazon.com/lambda/latest/dg/API_ListAliases.html,] the > functionVersion should not be required. From the history I've been able to > grab, it seems it was never required in which case I guess it should be fine > to relax the constraint. > > A workaround is to use pojoRequest and define the request explicitly by hand. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-17012) camel-aws2-lambda: ListAliases unduly return "Function Version must be specified to list aliases for a function"
Alex Dettinger created CAMEL-17012: -- Summary: camel-aws2-lambda: ListAliases unduly return "Function Version must be specified to list aliases for a function" Key: CAMEL-17012 URL: https://issues.apache.org/jira/browse/CAMEL-17012 Project: Camel Issue Type: Bug Components: camel-aws2 Affects Versions: 3.12.0 Reporter: Alex Dettinger Fix For: 3.13.., 3.11.3 The listAliases operation unduly fails in aws lambda. The underlying request is not built and the functionVersion parameter is unduly required. >From the doc >[https://docs.aws.amazon.com/lambda/latest/dg/API_ListAliases.html,] the >functionVersion should not be required. From the history I've been able to >grab, it seems it was never required in which case I guess it should be fine >to relax the constraint. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-17007) camel-aws2-lambda: GetAlias is not working
[ https://issues.apache.org/jira/browse/CAMEL-17007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-17007. Resolution: Fixed Backported to 3.11.x > camel-aws2-lambda: GetAlias is not working > -- > > Key: CAMEL-17007 > URL: https://issues.apache.org/jira/browse/CAMEL-17007 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.11.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.11.3, 3.12.0 > > > The getAlias operation is not working in camel-aws2-lambda. A workaround is > to use use pojoRequest and define the request explicitly by hand. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-17007) camel-aws2-lambda: GetAlias is not working
[ https://issues.apache.org/jira/browse/CAMEL-17007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-17007: --- Description: The getAlias operation is not working in camel-aws2-lambda. A workaround is to use use pojoRequest and define the request explicitly by hand. > camel-aws2-lambda: GetAlias is not working > -- > > Key: CAMEL-17007 > URL: https://issues.apache.org/jira/browse/CAMEL-17007 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > > The getAlias operation is not working in camel-aws2-lambda. A workaround is > to use use pojoRequest and define the request explicitly by hand. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-17007) camel-aws2-lambda: GetAlias is not working
[ https://issues.apache.org/jira/browse/CAMEL-17007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger reassigned CAMEL-17007: -- Assignee: Alex Dettinger > camel-aws2-lambda: GetAlias is not working > -- > > Key: CAMEL-17007 > URL: https://issues.apache.org/jira/browse/CAMEL-17007 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-17007) camel-aws2-lambda: GetAlias is not working
Alex Dettinger created CAMEL-17007: -- Summary: camel-aws2-lambda: GetAlias is not working Key: CAMEL-17007 URL: https://issues.apache.org/jira/browse/CAMEL-17007 Project: Camel Issue Type: Bug Components: camel-aws2 Reporter: Alex Dettinger -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16789) faulttolerance: timeoutScheduledExecutorServiceRef and bulkHead* to be deprecated ?
Alex Dettinger created CAMEL-16789: -- Summary: faulttolerance: timeoutScheduledExecutorServiceRef and bulkHead* to be deprecated ? Key: CAMEL-16789 URL: https://issues.apache.org/jira/browse/CAMEL-16789 Project: Camel Issue Type: Task Reporter: Alex Dettinger It looks like faulttolerance *timeoutScheduledExecutorServiceRef* and *bulkHead** have no effect. [FaultToleranceConfiguration.getTimeoutScheduledExecutorServiceRef()|https://github.com/apache/camel/blob/main/components/camel-microprofile/camel-microprofile-fault-tolerance/src/main/java/org/apache/camel/component/microprofile/faulttolerance/FaultToleranceConfiguration.java#L89..L91] is never called from camel code, so the configured value is never reified into an actual processor as far as I get it. Concerning bulkHead*, the [FaultToleranceReifier does not propagate|https://github.com/apache/camel/blob/main/components/camel-microprofile/camel-microprofile-fault-tolerance/src/main/java/org/apache/camel/component/microprofile/faulttolerance/FaultToleranceReifier.java#L103..L108] the bulkHeadEnabled boolean by calling something like *target.setBulkheadEnabled(true);* As such, the FaultToleranceProcessor never actually executes the [doStart()|https://github.com/apache/camel/blob/main/components/camel-microprofile/camel-microprofile-fault-tolerance/src/main/java/org/apache/camel/component/microprofile/faulttolerance/FaultToleranceProcessor.java#L348..L352] and [process()|https://github.com/apache/camel/blob/main/components/camel-microprofile/camel-microprofile-fault-tolerance/src/main/java/org/apache/camel/component/microprofile/faulttolerance/FaultToleranceProcessor.java#L239..L243] code related to bulkhead. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16643) camel-saxon: Remove the dependency to xslt-saxon
[ https://issues.apache.org/jira/browse/CAMEL-16643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-16643. Resolution: Fixed The removal of the useless dependency is solved [here|https://github.com/apache/camel/commit/3b3a9a00e401b97a17fcacf3d52c3af3969f2927]. The migration guide has been updated [here|https://github.com/apache/camel/commit/1fd27b28bf6890fe4f5724653d61ec1bcee6aa51]. > camel-saxon: Remove the dependency to xslt-saxon > > > Key: CAMEL-16643 > URL: https://issues.apache.org/jira/browse/CAMEL-16643 > Project: Camel > Issue Type: Improvement > Components: camel-saxon >Affects Versions: 3.9.0, 3.10.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.11.0 > > > It should be possible to remove the dependency to camel-xslt-saxon by moving > the tests out from camel-saxon. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-16643) camel-saxon: Remove the dependency to xslt-saxon
[ https://issues.apache.org/jira/browse/CAMEL-16643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352625#comment-17352625 ] Alex Dettinger edited comment on CAMEL-16643 at 5/27/21, 4:58 PM: -- [~davsclaus] , the failing tests mentioned are actually flaky ones that are not linked to this commit. I would suspect a kind of race condition where concurrent running tests using "System.setProperty(XPathFactory.DEFAULT_PROPERTY_NAME..." are mixing up. However, I was not able to find any evidence, nor a fix. Back to this ticket, I'm proposing an [update|https://github.com/apache/camel/pull/5605] of the 3.11 upgrade guide. I don't this there is community interest in backporting to 3.10 ? was (Author: aldettinger): [~davsclaus] , the failing tests mentioned are actually flaky ones that are not linked to this commit. I would suspect a kind of race condition where concurrent running tests using "System.setProperty(XPathFactory.DEFAULT_PROPERTY_NAME..." are mixing up. However, I was not able to find any evidence, nor a fix. Back to this ticket, I'm proposing an [update|https://github.com/apache/camel/pull/5605] of the 3.11 upgrade guide. Unless a backport to 3.10 was considered ? > camel-saxon: Remove the dependency to xslt-saxon > > > Key: CAMEL-16643 > URL: https://issues.apache.org/jira/browse/CAMEL-16643 > Project: Camel > Issue Type: Improvement > Components: camel-saxon >Affects Versions: 3.9.0, 3.10.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.11.0 > > > It should be possible to remove the dependency to camel-xslt-saxon by moving > the tests out from camel-saxon. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-16643) camel-saxon: Remove the dependency to xslt-saxon
[ https://issues.apache.org/jira/browse/CAMEL-16643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352625#comment-17352625 ] Alex Dettinger edited comment on CAMEL-16643 at 5/27/21, 4:51 PM: -- [~davsclaus] , the failing tests mentioned are actually flaky ones that are not linked to this commit. I would suspect a kind of race condition where concurrent running tests using "System.setProperty(XPathFactory.DEFAULT_PROPERTY_NAME..." are mixing up. However, I was not able to find any evidence, nor a fix. Back to this ticket, I'm proposing an [update|https://github.com/apache/camel/pull/5605] of the 3.11 upgrade guide. Unless a backport to 3.10 was considered ? was (Author: aldettinger): [~davsclaus] Claus, the failing tests mentioned are actually flaky ones that are not linked to this commit. I would suspect a kind of race condition where concurrent running tests using "System.setProperty(XPathFactory.DEFAULT_PROPERTY_NAME..." are mixing up. However, I was not able to find any evidence, nor a fix. Back to this ticket, I'm proposing an [update|https://github.com/apache/camel/pull/5605] of the 3.11 upgrade guide. Unless a backport to 3.10 was considered ? > camel-saxon: Remove the dependency to xslt-saxon > > > Key: CAMEL-16643 > URL: https://issues.apache.org/jira/browse/CAMEL-16643 > Project: Camel > Issue Type: Improvement > Components: camel-saxon >Affects Versions: 3.9.0, 3.10.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.11.0 > > > It should be possible to remove the dependency to camel-xslt-saxon by moving > the tests out from camel-saxon. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-16643) camel-saxon: Remove the dependency to xslt-saxon
[ https://issues.apache.org/jira/browse/CAMEL-16643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352625#comment-17352625 ] Alex Dettinger edited comment on CAMEL-16643 at 5/27/21, 4:51 PM: -- [~davsclaus] Claus, the failing tests mentioned are actually flaky ones that are not linked to this commit. I would suspect a kind of race condition where concurrent running tests using "System.setProperty(XPathFactory.DEFAULT_PROPERTY_NAME..." are mixing up. However, I was not able to find any evidence, nor a fix. Back to this ticket, I'm proposing an [update|https://github.com/apache/camel/pull/5605] of the 3.11 upgrade guide. Unless a backport to 3.10 was considered ? was (Author: aldettinger): @Claus, the failing tests mentioned are actually flaky ones that are not linked to this commit. I would suspect a kind of race condition where concurrent running tests using "System.setProperty(XPathFactory.DEFAULT_PROPERTY_NAME..." are mixing up. However, I was not able to find any evidence, nor a fix. Back to this ticket, I'm proposing an [update|https://github.com/apache/camel/pull/5605] of the 3.11 upgrade guide. Unless a backport to 3.10 was considered ? > camel-saxon: Remove the dependency to xslt-saxon > > > Key: CAMEL-16643 > URL: https://issues.apache.org/jira/browse/CAMEL-16643 > Project: Camel > Issue Type: Improvement > Components: camel-saxon >Affects Versions: 3.9.0, 3.10.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.11.0 > > > It should be possible to remove the dependency to camel-xslt-saxon by moving > the tests out from camel-saxon. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16643) camel-saxon: Remove the dependency to xslt-saxon
[ https://issues.apache.org/jira/browse/CAMEL-16643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352625#comment-17352625 ] Alex Dettinger commented on CAMEL-16643: @Claus, the failing tests mentioned are actually flaky ones that are not linked to this commit. I would suspect a kind of race condition where concurrent running tests using "System.setProperty(XPathFactory.DEFAULT_PROPERTY_NAME..." are mixing up. However, I was not able to find any evidence, nor a fix. Back to this ticket, I'm proposing an [update|https://github.com/apache/camel/pull/5605] of the 3.11 upgrade guide. Unless a backport to 3.10 was considered ? > camel-saxon: Remove the dependency to xslt-saxon > > > Key: CAMEL-16643 > URL: https://issues.apache.org/jira/browse/CAMEL-16643 > Project: Camel > Issue Type: Improvement > Components: camel-saxon >Affects Versions: 3.9.0, 3.10.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.11.0 > > > It should be possible to remove the dependency to camel-xslt-saxon by moving > the tests out from camel-saxon. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16643) camel-saxon: Remove the dependency to xslt-saxon
[ https://issues.apache.org/jira/browse/CAMEL-16643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-16643: --- Affects Version/s: 3.9.0 3.10.0 > camel-saxon: Remove the dependency to xslt-saxon > > > Key: CAMEL-16643 > URL: https://issues.apache.org/jira/browse/CAMEL-16643 > Project: Camel > Issue Type: Test >Affects Versions: 3.9.0, 3.10.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > > It should be possible to remove the dependency to camel-xslt-saxon by moving > the tests out from camel-saxon. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16643) camel-saxon: Remove the dependency to xslt-saxon
[ https://issues.apache.org/jira/browse/CAMEL-16643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-16643: --- Component/s: camel-saxon > camel-saxon: Remove the dependency to xslt-saxon > > > Key: CAMEL-16643 > URL: https://issues.apache.org/jira/browse/CAMEL-16643 > Project: Camel > Issue Type: Test > Components: camel-saxon >Affects Versions: 3.9.0, 3.10.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > > It should be possible to remove the dependency to camel-xslt-saxon by moving > the tests out from camel-saxon. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-16643) camel-saxon: Remove the dependency to xslt-saxon
[ https://issues.apache.org/jira/browse/CAMEL-16643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger reassigned CAMEL-16643: -- Assignee: Alex Dettinger > camel-saxon: Remove the dependency to xslt-saxon > > > Key: CAMEL-16643 > URL: https://issues.apache.org/jira/browse/CAMEL-16643 > Project: Camel > Issue Type: Test >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > > It should be possible to remove the dependency to camel-xslt-saxon by moving > the tests out from camel-saxon. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16643) camel-saxon: Remove the dependency to xslt-saxon
Alex Dettinger created CAMEL-16643: -- Summary: camel-saxon: Remove the dependency to xslt-saxon Key: CAMEL-16643 URL: https://issues.apache.org/jira/browse/CAMEL-16643 Project: Camel Issue Type: Test Reporter: Alex Dettinger It should be possible to remove the dependency to camel-xslt-saxon by moving the tests out from camel-saxon. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16543) bindy: add test for countGrapheme
[ https://issues.apache.org/jira/browse/CAMEL-16543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-16543. Fix Version/s: 3.10.0 Resolution: Fixed > bindy: add test for countGrapheme > - > > Key: CAMEL-16543 > URL: https://issues.apache.org/jira/browse/CAMEL-16543 > Project: Camel > Issue Type: Test > Components: camel-bindy >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.10.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16543) bindy: add test for countGrapheme
Alex Dettinger created CAMEL-16543: -- Summary: bindy: add test for countGrapheme Key: CAMEL-16543 URL: https://issues.apache.org/jira/browse/CAMEL-16543 Project: Camel Issue Type: Test Reporter: Alex Dettinger -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-16543) bindy: add test for countGrapheme
[ https://issues.apache.org/jira/browse/CAMEL-16543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger reassigned CAMEL-16543: -- Assignee: Alex Dettinger > bindy: add test for countGrapheme > - > > Key: CAMEL-16543 > URL: https://issues.apache.org/jira/browse/CAMEL-16543 > Project: Camel > Issue Type: Test >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16543) bindy: add test for countGrapheme
[ https://issues.apache.org/jira/browse/CAMEL-16543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-16543: --- Component/s: camel-bindy > bindy: add test for countGrapheme > - > > Key: CAMEL-16543 > URL: https://issues.apache.org/jira/browse/CAMEL-16543 > Project: Camel > Issue Type: Test > Components: camel-bindy >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16445) openstack: add some wiremock local integration tests
[ https://issues.apache.org/jira/browse/CAMEL-16445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-16445. Resolution: Fixed > openstack: add some wiremock local integration tests > > > Key: CAMEL-16445 > URL: https://issues.apache.org/jira/browse/CAMEL-16445 > Project: Camel > Issue Type: Test >Affects Versions: 3.9.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.10.0 > > > Based on openstack4j test data, it's possible to complete the test coverage > of camel-openstack with the help of wiremock. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16445) openstack: add some wiremock local integration tests
[ https://issues.apache.org/jira/browse/CAMEL-16445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-16445: --- Fix Version/s: 3.10.0 > openstack: add some wiremock local integration tests > > > Key: CAMEL-16445 > URL: https://issues.apache.org/jira/browse/CAMEL-16445 > Project: Camel > Issue Type: Test >Affects Versions: 3.9.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.10.0 > > > Based on openstack4j test data, it's possible to complete the test coverage > of camel-openstack with the help of wiremock. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16445) openstack: add some wiremock local integration tests
[ https://issues.apache.org/jira/browse/CAMEL-16445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-16445: --- Affects Version/s: 3.9.0 > openstack: add some wiremock local integration tests > > > Key: CAMEL-16445 > URL: https://issues.apache.org/jira/browse/CAMEL-16445 > Project: Camel > Issue Type: Test >Affects Versions: 3.9.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > > Based on openstack4j test data, it's possible to complete the test coverage > of camel-openstack with the help of wiremock. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16445) openstack: add some wiremock local integration tests
[ https://issues.apache.org/jira/browse/CAMEL-16445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-16445: --- Issue Type: Test (was: Bug) > openstack: add some wiremock local integration tests > > > Key: CAMEL-16445 > URL: https://issues.apache.org/jira/browse/CAMEL-16445 > Project: Camel > Issue Type: Test >Reporter: Alex Dettinger >Priority: Minor > > Based on openstack4j test data, it's possible to complete the test coverage > of camel-openstack with the help of wiremock. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16445) openstack: add some wiremock local integration tests
Alex Dettinger created CAMEL-16445: -- Summary: openstack: add some wiremock local integration tests Key: CAMEL-16445 URL: https://issues.apache.org/jira/browse/CAMEL-16445 Project: Camel Issue Type: Bug Reporter: Alex Dettinger Based on openstack4j test data, it's possible to complete the test coverage of camel-openstack with the help of wiremock. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-16445) openstack: add some wiremock local integration tests
[ https://issues.apache.org/jira/browse/CAMEL-16445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger reassigned CAMEL-16445: -- Assignee: Alex Dettinger > openstack: add some wiremock local integration tests > > > Key: CAMEL-16445 > URL: https://issues.apache.org/jira/browse/CAMEL-16445 > Project: Camel > Issue Type: Test >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > > Based on openstack4j test data, it's possible to complete the test coverage > of camel-openstack with the help of wiremock. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-16226) camel-cbor: Unexpected character ('¿' (code 191)): expected a valid value
[
https://issues.apache.org/jira/browse/CAMEL-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285766#comment-17285766
]
Alex Dettinger edited comment on CAMEL-16226 at 2/17/21, 10:29 AM:
---
I fix it in [this
commit|https://github.com/apache/camel/commit/e48fcd602622bc2dc59ce17faf7900bf3340a1c6]
it includes a test showing the scenario.
was (Author: aldettinger):
I fix it in
[https://github.com/apache/camel/commit/e48fcd602622bc2dc59ce17faf7900bf3340a1c6|https://github.com/apache/camel/commit/e48fcd602622bc2dc59ce17faf7900bf3340a1c6,]
the commit includes a test showing the scenario.
> camel-cbor: Unexpected character ('¿' (code 191)): expected a valid value
> -
>
> Key: CAMEL-16226
> URL: https://issues.apache.org/jira/browse/CAMEL-16226
> Project: Camel
> Issue Type: Bug
> Components: camel-cbor
>Affects Versions: 3.8.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-16226) camel-cbor: Unexpected character ('¿' (code 191)): expected a valid value
[
https://issues.apache.org/jira/browse/CAMEL-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285766#comment-17285766
]
Alex Dettinger edited comment on CAMEL-16226 at 2/17/21, 10:28 AM:
---
I fix it in
[https://github.com/apache/camel/commit/e48fcd602622bc2dc59ce17faf7900bf3340a1c6|https://github.com/apache/camel/commit/e48fcd602622bc2dc59ce17faf7900bf3340a1c6,]
the commit includes a test showing the scenario.
was (Author: aldettinger):
I fix it in
[https://github.com/apache/camel/commit/e48fcd602622bc2dc59ce17faf7900bf3340a1c6,]
the commit includes a test showing the scenario.
> camel-cbor: Unexpected character ('¿' (code 191)): expected a valid value
> -
>
> Key: CAMEL-16226
> URL: https://issues.apache.org/jira/browse/CAMEL-16226
> Project: Camel
> Issue Type: Bug
> Components: camel-cbor
>Affects Versions: 3.8.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] [Assigned] (CAMEL-16226) camel-cbor: Unexpected character ('¿' (code 191)): expected a valid value
[
https://issues.apache.org/jira/browse/CAMEL-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Dettinger reassigned CAMEL-16226:
--
Assignee: Alex Dettinger
> camel-cbor: Unexpected character ('¿' (code 191)): expected a valid value
> -
>
> Key: CAMEL-16226
> URL: https://issues.apache.org/jira/browse/CAMEL-16226
> Project: Camel
> Issue Type: Bug
> Components: camel-cbor
>Affects Versions: 3.8.0
>Reporter: Alex Dettinger
>Assignee: Alex Dettinger
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-16226) camel-cbor: Unexpected character ('¿' (code 191)): expected a valid value
[
https://issues.apache.org/jira/browse/CAMEL-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Dettinger resolved CAMEL-16226.
Fix Version/s: 3.9.0
Resolution: Fixed
> camel-cbor: Unexpected character ('¿' (code 191)): expected a valid value
> -
>
> Key: CAMEL-16226
> URL: https://issues.apache.org/jira/browse/CAMEL-16226
> Project: Camel
> Issue Type: Bug
> Components: camel-cbor
>Affects Versions: 3.8.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-16226) camel-cbor: Unexpected character ('¿' (code 191)): expected a valid value
[
https://issues.apache.org/jira/browse/CAMEL-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285766#comment-17285766
]
Alex Dettinger edited comment on CAMEL-16226 at 2/17/21, 10:26 AM:
---
I fix it in
[https://github.com/apache/camel/commit/e48fcd602622bc2dc59ce17faf7900bf3340a1c6,]
the commit includes a test showing the scenario.
was (Author: aldettinger):
I fix it in
[https://github.com/apache/camel/commit/e48fcd602622bc2dc59ce17faf7900bf3340a1c6,]
the commit include a test showing the scenario.
> camel-cbor: Unexpected character ('¿' (code 191)): expected a valid value
> -
>
> Key: CAMEL-16226
> URL: https://issues.apache.org/jira/browse/CAMEL-16226
> Project: Camel
> Issue Type: Bug
> Components: camel-cbor
>Affects Versions: 3.8.0
>Reporter: Alex Dettinger
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16226) camel-cbor: Unexpected character ('¿' (code 191)): expected a valid value
[
https://issues.apache.org/jira/browse/CAMEL-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285766#comment-17285766
]
Alex Dettinger commented on CAMEL-16226:
I fix it in
[https://github.com/apache/camel/commit/e48fcd602622bc2dc59ce17faf7900bf3340a1c6,]
the commit include a test showing the scenario.
> camel-cbor: Unexpected character ('¿' (code 191)): expected a valid value
> -
>
> Key: CAMEL-16226
> URL: https://issues.apache.org/jira/browse/CAMEL-16226
> Project: Camel
> Issue Type: Bug
> Components: camel-cbor
>Affects Versions: 3.8.0
>Reporter: Alex Dettinger
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-16226) camel-cbor: Unexpected character ('¿' (code 191)): expected a valid value
Alex Dettinger created CAMEL-16226:
--
Summary: camel-cbor: Unexpected character ('¿' (code 191)):
expected a valid value
Key: CAMEL-16226
URL: https://issues.apache.org/jira/browse/CAMEL-16226
Project: Camel
Issue Type: Bug
Components: camel-cbor
Affects Versions: 3.8.0
Reporter: Alex Dettinger
--
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] [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] [Assigned] (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 reassigned CAMEL-16168: -- Assignee: Alex Dettinger > 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 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16168) camel-oaipmh: Replace the JettyTestServer with wiremock
Alex Dettinger created CAMEL-16168: -- Summary: 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 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15997) camel-redis: Port the test to camel-test-infra
[ https://issues.apache.org/jira/browse/CAMEL-15997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-15997. Fix Version/s: 3.8.0 Resolution: Fixed Fixed in https://github.com/apache/camel/commit/d85f230d1b7acaee2594e5fc1b561dd2e4eb3268 > camel-redis: Port the test to camel-test-infra > -- > > Key: CAMEL-15997 > URL: https://issues.apache.org/jira/browse/CAMEL-15997 > 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-15997) camel-redis: Move the test to camel-test-infra
[ https://issues.apache.org/jira/browse/CAMEL-15997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-15997: --- Summary: camel-redis: Move the test to camel-test-infra (was: camel-redis: Make test test container based) > camel-redis: Move the test to camel-test-infra > -- > > Key: CAMEL-15997 > URL: https://issues.apache.org/jira/browse/CAMEL-15997 > Project: Camel > Issue Type: New Feature >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15997) camel-redis: Port the test to camel-test-infra
[ https://issues.apache.org/jira/browse/CAMEL-15997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-15997: --- Summary: camel-redis: Port the test to camel-test-infra (was: camel-redis: Move the test to camel-test-infra) > camel-redis: Port the test to camel-test-infra > -- > > Key: CAMEL-15997 > URL: https://issues.apache.org/jira/browse/CAMEL-15997 > Project: Camel > Issue Type: New Feature >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-15997) camel-redis: Make test test container based
[ https://issues.apache.org/jira/browse/CAMEL-15997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger reassigned CAMEL-15997: -- Assignee: Alex Dettinger > camel-redis: Make test test container based > --- > > Key: CAMEL-15997 > URL: https://issues.apache.org/jira/browse/CAMEL-15997 > Project: Camel > Issue Type: New Feature >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15997) camel-redis: Make test test container based
Alex Dettinger created CAMEL-15997: -- Summary: camel-redis: Make test test container based Key: CAMEL-15997 URL: https://issues.apache.org/jira/browse/CAMEL-15997 Project: Camel Issue Type: New Feature Reporter: Alex Dettinger -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15981) Consider aligning gson versions accross camel dependencies
[ https://issues.apache.org/jira/browse/CAMEL-15981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-15981: --- Description: See discussion in context here: [https://github.com/apache/camel-quarkus/pull/2088#discussion_r546605397]. Keep in mind that 2.8.6 doesn't work in OSGi. was:See discussion in context here: https://github.com/apache/camel-quarkus/pull/2088#discussion_r546605397. > Consider aligning gson versions accross camel dependencies > -- > > Key: CAMEL-15981 > URL: https://issues.apache.org/jira/browse/CAMEL-15981 > Project: Camel > Issue Type: New Feature >Reporter: Alex Dettinger >Priority: Minor > > See discussion in context here: > [https://github.com/apache/camel-quarkus/pull/2088#discussion_r546605397]. > Keep in mind that 2.8.6 doesn't work in OSGi. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15981) Consider aligning gson versions accross camel dependencies
Alex Dettinger created CAMEL-15981: -- Summary: Consider aligning gson versions accross camel dependencies Key: CAMEL-15981 URL: https://issues.apache.org/jira/browse/CAMEL-15981 Project: Camel Issue Type: New Feature Reporter: Alex Dettinger See discussion in context here: https://github.com/apache/camel-quarkus/pull/2088#discussion_r546605397. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15837) camel-nats: add an option to enable connection protocol fine tracing
[ https://issues.apache.org/jira/browse/CAMEL-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-15837. Fix Version/s: 3.7.0 Resolution: Fixed > camel-nats: add an option to enable connection protocol fine tracing > > > Key: CAMEL-15837 > URL: https://issues.apache.org/jira/browse/CAMEL-15837 > Project: Camel > Issue Type: New Feature > Components: camel-nats >Affects Versions: 3.6.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.7.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-15837) camel-nats: add an option to enable connection protocol fine tracing
[ https://issues.apache.org/jira/browse/CAMEL-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger reassigned CAMEL-15837: -- Assignee: Alex Dettinger > camel-nats: add an option to enable connection protocol fine tracing > > > Key: CAMEL-15837 > URL: https://issues.apache.org/jira/browse/CAMEL-15837 > Project: Camel > Issue Type: New Feature > Components: camel-nats >Affects Versions: 3.6.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15837) camel-nats: add an option to enable connection protocol fine tracing
Alex Dettinger created CAMEL-15837: -- Summary: camel-nats: add an option to enable connection protocol fine tracing Key: CAMEL-15837 URL: https://issues.apache.org/jira/browse/CAMEL-15837 Project: Camel Issue Type: New Feature Components: camel-nats Affects Versions: 3.6.0 Reporter: Alex Dettinger -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15767) Complete camel-nagios tests with a mock nsca server based test
[ https://issues.apache.org/jira/browse/CAMEL-15767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-15767. Resolution: Fixed Fixed here: [https://github.com/apache/camel/commit/ede1347be948a3a955243010b8dc6c535d3a6f4b] > Complete camel-nagios tests with a mock nsca server based test > -- > > Key: CAMEL-15767 > URL: https://issues.apache.org/jira/browse/CAMEL-15767 > Project: Camel > Issue Type: Test > Components: camel-nagios >Affects Versions: 3.6.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.7.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15767) Complete camel-nagios tests with a mock nsca server based test
[ https://issues.apache.org/jira/browse/CAMEL-15767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-15767: --- Fix Version/s: 3.7.0 > Complete camel-nagios tests with a mock nsca server based test > -- > > Key: CAMEL-15767 > URL: https://issues.apache.org/jira/browse/CAMEL-15767 > Project: Camel > Issue Type: Test > Components: camel-nagios >Affects Versions: 3.6.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.7.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15767) Complete camel-nagios tests with a mock nsca server based test
[ https://issues.apache.org/jira/browse/CAMEL-15767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-15767: --- Summary: Complete camel-nagios tests with a mock nsca server based test (was: Complete camel-nagios test with test based on a mock nsca server) > Complete camel-nagios tests with a mock nsca server based test > -- > > Key: CAMEL-15767 > URL: https://issues.apache.org/jira/browse/CAMEL-15767 > Project: Camel > Issue Type: Test > Components: camel-nagios >Affects Versions: 3.6.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-15767) Complete camel-nagios test with test based on a mock nsca server
[ https://issues.apache.org/jira/browse/CAMEL-15767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger reassigned CAMEL-15767: -- Assignee: Alex Dettinger > Complete camel-nagios test with test based on a mock nsca server > > > Key: CAMEL-15767 > URL: https://issues.apache.org/jira/browse/CAMEL-15767 > Project: Camel > Issue Type: Test > Components: camel-nagios >Affects Versions: 3.6.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15767) Complete camel-nagios tests with a mock nsca server based test
[ https://issues.apache.org/jira/browse/CAMEL-15767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-15767: --- Summary: Complete camel-nagios tests with a mock nsca server based test (was: Complete camel-nagios tests with a mock ncsa server based test) > Complete camel-nagios tests with a mock nsca server based test > -- > > Key: CAMEL-15767 > URL: https://issues.apache.org/jira/browse/CAMEL-15767 > Project: Camel > Issue Type: Test > Components: camel-nagios >Affects Versions: 3.6.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15767) Complete camel-nagios tests with a mock ncsa server based test
[ https://issues.apache.org/jira/browse/CAMEL-15767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-15767: --- Summary: Complete camel-nagios tests with a mock ncsa server based test (was: Complete camel-nagios tests with a mock nsca server based test) > Complete camel-nagios tests with a mock ncsa server based test > -- > > Key: CAMEL-15767 > URL: https://issues.apache.org/jira/browse/CAMEL-15767 > Project: Camel > Issue Type: Test > Components: camel-nagios >Affects Versions: 3.6.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15767) Complete camel-nagios test with test based on a mock nsca server
Alex Dettinger created CAMEL-15767: -- Summary: Complete camel-nagios test with test based on a mock nsca server Key: CAMEL-15767 URL: https://issues.apache.org/jira/browse/CAMEL-15767 Project: Camel Issue Type: Test Components: camel-nagios Affects Versions: 3.6.0 Reporter: Alex Dettinger -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (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 reassigned CAMEL-15635: -- Assignee: Alex Dettinger > 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 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel=17219206#comment-17219206 ] Alex Dettinger commented on CAMEL-15635: Should be fixed with Kudu 1.14, though the release may not be available that soon. > 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 >Priority: Major > -- 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 ] Alex Dettinger updated CAMEL-15635: --- Summary: Some Kudu tests are failing in JDK >= 12 builds (was: Some Kudu tests are failing in JDK 14) > 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 >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15635) Some Kudu tests are failing in JDK 14
[ https://issues.apache.org/jira/browse/CAMEL-15635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17208044#comment-17208044 ] Alex Dettinger commented on CAMEL-15635: Linked to [KUDU-3200|https://issues.apache.org/jira/browse/KUDU-3200]. > Some Kudu tests are failing in JDK 14 > - > > 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 >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15635) Some Kudu tests are failing in JDK 14
Alex Dettinger created CAMEL-15635: -- Summary: Some Kudu tests are failing in JDK 14 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 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15614) camel-pg-replicationslot: Automate integration test
[ https://issues.apache.org/jira/browse/CAMEL-15614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-15614: --- Fix Version/s: 3.6.0 > camel-pg-replicationslot: Automate integration test > --- > > Key: CAMEL-15614 > URL: https://issues.apache.org/jira/browse/CAMEL-15614 > Project: Camel > Issue Type: Test > Components: camel-pg-replicationslot >Affects Versions: 3.5.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.6.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15614) camel-pg-replicationslot: Automate integration test
[ https://issues.apache.org/jira/browse/CAMEL-15614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-15614. Resolution: Fixed > camel-pg-replicationslot: Automate integration test > --- > > Key: CAMEL-15614 > URL: https://issues.apache.org/jira/browse/CAMEL-15614 > Project: Camel > Issue Type: Test > Components: camel-pg-replicationslot >Affects Versions: 3.5.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.6.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15614) camel-pg-replicationslot: Automate integration test
[ https://issues.apache.org/jira/browse/CAMEL-15614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-15614: --- Summary: camel-pg-replicationslot: Automate integration test (was: camel-pg-replicationslot: Automated integration test) > camel-pg-replicationslot: Automate integration test > --- > > Key: CAMEL-15614 > URL: https://issues.apache.org/jira/browse/CAMEL-15614 > Project: Camel > Issue Type: Test > Components: camel-pg-replicationslot >Affects Versions: 3.5.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15614) camel-pg-replicationslot: Automated integration test
Alex Dettinger created CAMEL-15614: -- Summary: camel-pg-replicationslot: Automated integration test Key: CAMEL-15614 URL: https://issues.apache.org/jira/browse/CAMEL-15614 Project: Camel Issue Type: Test Components: camel-pg-replicationslot Affects Versions: 3.5.0 Reporter: Alex Dettinger -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-15614) camel-pg-replicationslot: Automated integration test
[ https://issues.apache.org/jira/browse/CAMEL-15614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger reassigned CAMEL-15614: -- Assignee: Alex Dettinger > camel-pg-replicationslot: Automated integration test > > > Key: CAMEL-15614 > URL: https://issues.apache.org/jira/browse/CAMEL-15614 > Project: Camel > Issue Type: Test > Components: camel-pg-replicationslot >Affects Versions: 3.5.0 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
