Allow greater aws-java-sdk version flexibility
jklukas opened this issue · 1 comments
Currently, AWScala modules specify aws-java-sdk components as transitive dependencies, with a global version set for the entire AWScala project. There are, however, many scenarios where a user might want to fine-tune the version of the underlying aws-java-sdk they're using.
A comprehensive solution could be to mark all aws-java-sdk dependencies as "provided" scope and document that the user is expected to define dependencies on all used AWS modules. We could then set individual minimum supported AWS SDK versions per submodule; those versions would be used to compile the AWScala jars, but end users would then be free to use any newer version of aws-java-sdk components as they see fit.
This would unfortunately be a breaking change since it requires users to update their dependency lists to include the aws-java-sdk modules. If there's support for this idea, I would be willing to implement it. Hoping to gauge interest first, though.
Thanks for this project!
Seems that this currently expects AWS SDK v 1, not v2
https://docs.aws.amazon.com/sdk-for-java/v2/developer-guide/
Would be nice if it could use v2