Discussion: AWS SDK broken by change in Jackson DataBind
The version line was removed in pom.xml for jackson data-bind. This was done in the 0.3.8 version of the lib.
This has caused the AWS SDK to stop working with the following error:
java.lang.NoClassDefFoundError: Could not initialize class com.amazonaws.ClientConfiguration
at com.amazonaws.ClientConfigurationFactory.getDefaultConfig(ClientConfigurationFactory.java:46)
at com.amazonaws.ClientConfigurationFactory.getConfig(ClientConfigurationFactory.java:36)
at com.amazonaws.client.builder.AwsClientBuilder.resolveClientConfiguration(AwsClientBuilder.java:169)
at com.amazonaws.client.builder.AwsClientBuilder.access$000(AwsClientBuilder.java:54)
at com.amazonaws.client.builder.AwsClientBuilder$SyncBuilderParams.<init>(AwsClientBuilder.java:505)
at com.amazonaws.client.builder.AwsClientBuilder.getSyncClientParams(AwsClientBuilder.java:441)
at com.amazonaws.client.builder.AwsSyncClientBuilder.build(AwsSyncClientBuilder.java:46)
at org.opengroup.osdu.core.aws.cognito.CognitoBuilder.generateCognitoClient(CognitoBuilder.java:25)
at org.opengroup.osdu.core.aws.cognito.AWSCognitoClient.<init>(AWSCognitoClient.java:54)
I would like to find out the following:
- What is the version of Jackson Core/Databind now being used since version is unset in the POM
- What is the minimum version the CVS being resolved required us to adopt (in case I need to match to AWS SDK versions)