Deprecate v1 sdk #5088
Replies: 2 comments
-
We are adding Migrating to AWS SDK for Java v2 information to the top description of some handwritten classes, like RequestHandler2 and EC2MetadataUtils. For a more granular v1-to-v2 mapping, including API differences and behavior changes, this information will be added to the Migrate to version 2 section of the Developer Guide - for example: The "Migrate to version 2" documentation is a work in progress, we are actively working on it and constantly adding new pages. We understand DynamoDB Enhanced client is missing right now, and it's a highly needed documentation. I don't think we'll be able to add the v2 equivalent classes to all the v1 Javadocs, because most v1 classes are auto-generated, and the logic to find the v2 equivalent is not always straightforward. |
Beta Was this translation helpful? Give feedback.
-
It is crazy that aws sdk v2 was released in 2018 and migration guides are still a work in progress in 2024. If aws devs find the logic hard to find the v2 equivalent of classes, imagine how a consumer of the api feels! It is always nice to visually see and be warned when you are using a deprecated class in your IDE and for the javadoc help guide you to its replacement. Was just trying to throw out a suggestion that would help your consumers. |
Beta Was this translation helpful? Give feedback.
-
Amazon has announced the end of support for aws sdk v1. Why do they not deprecate the classes and add javadocs letting devs know what new class to use instead?
Beta Was this translation helpful? Give feedback.
All reactions