The Amazon SDK for Java version 1.12 upgrades its dependency on Jackson

{"value":"We are raising the minor version of AWS SDK for Java from 1.11 to 1.12 in order to upgrade the SDK’s dependency on the popular third-party JSON library, Jackson. This release does not change any of the AWS SDK APIs. Even though there are some backwards-incompatible changes in Jackson APIs, it should be a straight-forward upgrade for the majority of our current customers.\n\n#### **Why are we upgrading the dependency on Jackson?**\n\nThe AWS SDK for Java 1.11 was using Jackson 2.6, which is an old version that is missing numerous improvements that are present in the latest version of Jackson.\n\n#### **How does this Jackson upgrade affect your applications?**\n\nIf you only use Jackson through the AWS SDK for Java, there is nothing you need to do – your application will not be affected. However, if your application was using a Jackson version prior to 2.12 directly or through libraries other than the AWS SDK, you may observe behavioral changes or compile-time errors relating to Jackson classes once you upgrade to the AWS SDK version 1.12. You can see which version of Jackson your application is using by running\n```mvn dependency:list```or```gradle dependencies```.\n\nYou should thoroughly test all non-SDK use cases to ensure that they are not inversely impacted by the new version of Jackson. If they are inversely impacted, we recommend upgrading those use cases to support 2.12 to ensure that your application has all of the improvements in the latest Jackson version.\n\nIf you have any questions or concerns, you can [contact us on Github](https://github.com/aws/aws-sdk-java/issues).\n\n\n\n\n\n","render":"<p>We are raising the minor version of AWS SDK for Java from 1.11 to 1.12 in order to upgrade the SDK’s dependency on the popular third-party JSON library, Jackson. This release does not change any of the AWS SDK APIs. Even though there are some backwards-incompatible changes in Jackson APIs, it should be a straight-forward upgrade for the majority of our current customers.</p>\n<h4><a id=\"Why_are_we_upgrading_the_dependency_on_Jackson_2\"></a><strong>Why are we upgrading the dependency on Jackson?</strong></h4>\n<p>The AWS SDK for Java 1.11 was using Jackson 2.6, which is an old version that is missing numerous improvements that are present in the latest version of Jackson.</p>\n<h4><a id=\"How_does_this_Jackson_upgrade_affect_your_applications_6\"></a><strong>How does this Jackson upgrade affect your applications?</strong></h4>\n<p>If you only use Jackson through the AWS SDK for Java, there is nothing you need to do – your application will not be affected. However, if your application was using a Jackson version prior to 2.12 directly or through libraries other than the AWS SDK, you may observe behavioral changes or compile-time errors relating to Jackson classes once you upgrade to the AWS SDK version 1.12. You can see which version of Jackson your application is using by running<br />\n<code>mvn dependency:list</code>or<code>gradle dependencies</code>.</p>\n<p>You should thoroughly test all non-SDK use cases to ensure that they are not inversely impacted by the new version of Jackson. If they are inversely impacted, we recommend upgrading those use cases to support 2.12 to ensure that your application has all of the improvements in the latest Jackson version.</p>\n<p>If you have any questions or concerns, you can <a href=\"https://github.com/aws/aws-sdk-java/issues\" target=\"_blank\">contact us on Github</a>.</p>\n"}