Scala 2.11 support/AWS EMR compatibility about awscala

[seratch]

Is it generally safe to link a later version of the AWS Java SDK to a version of AWScala that depends on an earlier version?

It depends but it may not be safe for some cases. The AWS Java SDK releases are not binary-compatible even among patch versions. So, linking a different version can be a cause of runtime errors.

I don't want to have cross builds with Scala 2.11 for this entire project anymore. But you have the necessity to have scala 2.11 builds specifically for the EMR module, I'm open to the idea to ship scala 2.11 builds only for it. The cross-build won't be so complex probably. Personally, I don't have much time to spend on it. I would like to have some contributions on it from the user community.

[Liam3851]

I can't speak to other users, but the parts of AWScala I use on EMR primarily are the SQS module and the S3 module.. the EMR module itself is mostly for starting/managing clusters (which I do on machines that aren't themselves EMR clusters); once I'm on the cluster I don't really need the EMR submodule anymore.

That said, I understand the desire not to manage cross-builds esp. for a version of Scala now two revisions out of date and deprecated even for Spark.

I'm not super-familiar with the internals of AWScala or its build procedure, but if I were to fork and then revert to the build code to the code prior to #215, how hard would it be for me to build a custom 2.11-compatible artifact against the newer Java SDK?

[Liam3851]

EMR from version 6.0.0 supports Scala 2.12. Closing.