We’re elevating the minor model of AWS SDK for Java from 1.11 to 1.12 with the intention to improve the SDK’s dependency on the favored third-party JSON library, Jackson. This launch doesn’t change any of the AWS SDK APIs. Despite the fact that there are some backwards-incompatible adjustments in Jackson APIs, it needs to be a straight-forward improve for almost all of our present clients.
Why are we upgrading the dependency on Jackson?
The AWS SDK for Java 1.11 was utilizing Jackson 2.6, which is an previous model that’s lacking quite a few enhancements which might be current within the newest model of Jackson.
How does this Jackson improve have an effect on your purposes?
When you solely use Jackson by the AWS SDK for Java, there’s nothing it’s essential to do – your software won’t be affected. Nonetheless, in case your software was utilizing a Jackson model previous to 2.12 straight or by libraries aside from the AWS SDK, you could observe behavioral adjustments or compile-time errors referring to Jackson lessons when you improve to the AWS SDK model 1.12. You may see which model of Jackson your software is utilizing by operating mvn dependency:checklist or gradle dependencies.
You need to totally take a look at all non-SDK use instances to make sure that they don’t seem to be inversely impacted by the brand new model of Jackson. If they’re inversely impacted, we suggest upgrading these use instances to help 2.12 to make sure that your software has the entire enhancements within the newest Jackson model.
When you have any questions or considerations, you may contact us on Github.
