[
https://issues.apache.org/jira/browse/CAMEL-23003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18058430#comment-18058430
]
Aurélien Pupier edited comment on CAMEL-23003 at 2/13/26 12:52 PM:
-------------------------------------------------------------------
com.amazonaws:aws-java-sdk-core:jar:1.12.150:test seems a bit old (2022)
there is a 1.12.797 released at the end of 2025.
And another point is that this artifact has been marked as relocated to
software.amazon.awssdk » aws-core
I'm wondering why this dependency was not updated automatically via dependabot
(or is it a transitive dependency?)
was (Author: apupier):
com.amazonaws:aws-java-sdk-core:jar:1.12.150:test seems a bit old (2022)
there is a 1.12.797 released at the end of 2025.
And another point is that this artifact has been marked as relocated to
software.amazon.awssdk » aws-core
I'm wondering why this dependency was not updated automatically via
dependencaot (or is it a transitive dependency?)
> camel-test-infra - Align Jackson JARs for testcontainers
> --------------------------------------------------------
>
> Key: CAMEL-23003
> URL: https://issues.apache.org/jira/browse/CAMEL-23003
> Project: Camel
> Issue Type: Improvement
> Components: camel-test-infra
> Affects Versions: 4.18.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.18.1, 4.19.0
>
>
> The example in CAMEL-22999 with aws is failing because we have mixed old
> versions of Jackson JARs when using test containers and test-infra
> Because test-infra is using <scope>test-jar</scope> then maven cannot handle
> dependency correctly, and you end up with older jackson JARs.
> So we need to explicit declare jackson jars in every pom.xml for test-infra
> that is testcontainer based.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
