[
https://issues.apache.org/jira/browse/CAMEL-13784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014274#comment-17014274
]
Luca Burgazzoli commented on CAMEL-13784:
-----------------------------------------
I think we should seriously start looking into this as I fear v1 will be
deprecated soon or later and we'll have to rush.
We could have the "v2" components living side by side with the "v1" ones and
name them like camel-aws2-${target} and deprecated the v1s as soon as a new v2
component is ready.
> Update to AWS SDK V2
> --------------------
>
> Key: CAMEL-13784
> URL: https://issues.apache.org/jira/browse/CAMEL-13784
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws
> Reporter: Pierre-Yves Bigourdan
> Priority: Major
> Fix For: Future
>
>
> The [AWS SDK for Java 2.0|https://github.com/aws/aws-sdk-java-v2] reached
> general availability back in November 2018 (more information on their
> [official blog
> post|https://aws.amazon.com/blogs/developer/aws-sdk-for-java-2-x-released])
> and has de facto become the preferred way of integrating with AWS using Java.
> Amongst other benefits, using it rather than the old version improves
> performance and allows to write cleaner code, as it supports more modern
> language constructs and has a consistent API across the different services.
> The V1 SDK has not yet been officially deprecated, however Camel will need
> updating at some point, especially as more and more applications are being
> migrated to use the V2 SDK.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
