-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for AWS Java SDK v2 #5
Comments
Thank you for reaching out with this request. The AWS Java SDK v2 was released in November and we have not yet investigated this. Incorporating AWS Java SDK v2 will be considered for a future release. |
see: #6 |
see more recent SDK #13 with 2.15.19 |
We reviewed your request and in-order to prioritize it, we would like to understand your use-case to use SDKv2 over SDKv1. The two versions of the AWS SDK for Java can work together side-by-side without issue. |
@simonmarty , |
@simonmarty they can work side by side but that's good as a temporary workaround not as a final solution. Why would I want to have 2 versions of the same library in my classpath? |
This is unsatisfactory reason to dismiss this feature request. SDKv2 exists to replace v1. As such, tools like this one should be supporting, and promoting V2 usage. Not challenging its value like this answer. |
Closes #5 *Description of changes:* Provide a major version 2 version of the Java Caching Library. Version 2 uses the Java SDK v2 under the hood. The library should be a drop-in replacement, unless you currently provide a v1 client to the caching library at creation. In that case, you will have to start passing a v2 client instead. Version 1 and version 2 will be maintained side by side in separate branches. By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
AWS Java SDK v2 was launched last year https://aws.amazon.com/blogs/developer/aws-sdk-for-java-2-x-released/
It would be nice to have this caching classes with the new API
The text was updated successfully, but these errors were encountered: