-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scala 2.13 cross compilation #2893
Comments
source: https://twitter.com/SethTisue/status/1372340143529467905?s=20 |
This issue is closed because the MR (#3294) above was merged. However, when I look on Maven Central for the Scala 2.13 versions, it appears they weren't published as part of the 3.6.0 release. i.e. https://search.maven.org/search?q=org.locationtech.geotrellis Both links above show no 2.13 binaries available. When can we expect 2.13 binaries to be published? |
Hey @jessewebb, that's correct. We are blocked by the Spark 3.2.0 release now. I think the ETA for that is ~ September / October. The 2.13 crosscompilation relies on the Spark 3.2.0-SNAPSHOT, because of this reason we publish only 2.13 snapshots that can be found here: https://repo.eclipse.org/content/groups/snapshots/org/locationtech/geotrellis/ |
Thank you for the quick response! We are moving our codebases to 2.13 and we are just using the |
With Spark 3.2.0 released in Oct, would it be possible to get a 2.13 build? |
hey @waveskimmer will publish it soon, for now I would recommend you to use SNAPSHOTS, we don't really plan to do any changes before the release. |
Basing on the following information
https://spark.apache.org/news/spark-2-4-1-released.html
And this JIRA ticket, I suppose we need to move along with the Spark.
Probably 2.13 support would be in Spark 3.0 release. The result of this issue would be to drop Scala 2.11 and to add Scala 2.12 and 2.13 cross compilation (for sure if there would be Spark binaries).
This issue will also contain changes that would be nice to have to simplify Scala 3 migration:
Scala 2.13
Traversable
(it is possible to replace it withIterable
)TraversableOnce
(it is possible to replace it withIterableOnce
)Scala 3
def foo()
can be called only as a.foo()
in the code and can't be invoked as.foo
without parentheses (see https://scastie.scala-lang.org/pzjfiB1VT1C9Aljp9YkzMQ). So Scala would be more strict about it.do
loops would be removed; instead, it would be possible to use a newwhile
notationThe text was updated successfully, but these errors were encountered: