You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have confirmed that aws sdk v2 comes bundled with "software.amazon.awssdk:third-party-jackson-core", so if a dev team is including either jackson-databind or jackson-jr, they are duplicating jackson dependencies, etc
What is correct? Please update docs to reflect the correct route devs should take.
Describe the issue
Here AWS advises devs to use jackson-jr if you are trying to make your jars as small as possible for AWS lambda's sake. https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/lambda-optimize-starttime.html
And then here you state AWS decided to roll their own jackson depedency.
https://aws.amazon.com/blogs/developer/the-aws-sdk-for-java-2-17-removes-its-external-dependency-on-jackson/
I have confirmed that aws sdk v2 comes bundled with "software.amazon.awssdk:third-party-jackson-core", so if a dev team is including either jackson-databind or jackson-jr, they are duplicating jackson dependencies, etc
What is correct? Please update docs to reflect the correct route devs should take.
Links
https://aws.amazon.com/blogs/developer/the-aws-sdk-for-java-2-17-removes-its-external-dependency-on-jackson/
https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/lambda-optimize-starttime.html
The text was updated successfully, but these errors were encountered: