Resolving Conflicts between AWS Versions

[stwhite]

I'm new to Spring Cloud and AWS and having some issues resolving what I think is a conflict between AWS versions required by two different dependencies.

I'm looking to use Spring Cloud for AWS 2.3.1 and it wants the AWS Java SDK version 1.11.951.
In our project we have another dependency that is using AWS and it wants version 1.11.942.

Using Gradle's dependency insights, it determines that the former version is what going to be used.

However, we are getting the following exception when starting the service and its trying to create the simpleMessageListenerCotainer.

Caused by: java.lang.NoSuchFieldError: CLIENT_ENDPOINT at com.amazonaws.services.sqs.AmazonSQSClient.executeGetQueueUrl(AmazonSQSClient.java:1216) ~[aws-java-sdk-sqs-1.11.951.jar:na] at com.amazonaws.services.sqs.AmazonSQSClient.getQueueUrl(AmazonSQSClient.java:1198) ~[aws-java-sdk-sqs-1.11.951.jar:na] at com.amazonaws.services.sqs.buffered.AmazonSQSBufferedAsyncClient.getQueueUrl(AmazonSQSBufferedAsyncClient.java:261) ~[aws-java-sdk-sqs-1.11.951.jar:na] at io.awspring.cloud.messaging.support.destination.DynamicQueueUrlDestinationResolver.resolveDestination(DynamicQueueUrlDestinationResolver.java:90) ~[spring-cloud-aws-messaging-2.3.1.jar:2.3.1] at io.awspring.cloud.messaging.support.destination.DynamicQueueUrlDestinationResolver.resolveDestination(DynamicQueueUrlDestinationResolver.java:38) ~[spring-cloud-aws-messaging-2.3.1.jar:2.3.1] at org.springframework.messaging.core.CachingDestinationResolverProxy.resolveDestination(CachingDestinationResolverProxy.java:92) ~[spring-messaging-5.3.6.jar:5.3.6] at io.awspring.cloud.messaging.listener.AbstractMessageListenerContainer.queueAttributes(AbstractMessageListenerContainer.java:328) ~[spring-cloud-aws-messaging-2.3.1.jar:2.3.1] at io.awspring.cloud.messaging.listener.AbstractMessageListenerContainer.initialize(AbstractMessageListenerContainer.java:302) ~[spring-cloud-aws-messaging-2.3.1.jar:2.3.1] at io.awspring.cloud.messaging.listener.SimpleMessageListenerContainer.initialize(SimpleMessageListenerContainer.java:116) ~[spring-cloud-aws-messaging-2.3.1.jar:2.3.1] at io.awspring.cloud.messaging.listener.AbstractMessageListenerContainer.afterPropertiesSet(AbstractMessageListenerContainer.java:269) ~[spring-cloud-aws-messaging-2.3.1.jar:2.3.1] at io.awspring.cloud.messaging.listener.SimpleMessageListenerContainer.afterPropertiesSet(SimpleMessageListenerContainer.java:50) ~[spring-cloud-aws-messaging-2.3.1.jar:2.3.1] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1845) ~[spring-beans-5.3.6.jar:5.3.6] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1782) ~[spring-beans-5.3.6.jar:5.3.6] ... 17 common frames omitted

Is this due to the mismatched library dependencies on AWS even though gradle seems to resolve them to the version Spring Cloud is expecting?

Or any other clues as to what might be going on here?

Any help would be much appreciated.

Thank you!

[maciejwalkowiak]

Apologies for late reply.

This means that some of the AWS dependencies are in 1.11.951 and some in 1.11.942, in this case SQS uses 1.11.951 and aws-java-sdk-core uses 1.11.942. Make sure that all AWS SDK dependencies use the same version.