-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Merge 2.11 to 2.12 #5055
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
Merge 2.11 to 2.12 #5055
Conversation
there shouldn't be user-visible changes since 1.0.4, but regardless, it's good to depend on the latest
might as well let people have the current stuff. I asked the Akka folks and nobody saw a reason not to upgrade. this version of Akka is the latest in the 2.3.x series, but is also some months old, so no stability worries. (this would have been included in 2.11.8 if I had thought of it in time)
bundle a newer Akka actors jar
0e7005e
to
3721775
Compare
Review by @szeiger. The changes to the sbt import scripts for 2.12.x are in a separate commit. The change of the akka-actors in 2.11.x doesn't apply to 2.12.x (we don't pull in akka-actors anymore). |
….12.x Includes tests to verify the toString representations.
upgrade to latest scala-xml (namely 1.0.5)
…ring-√ SI-9488 - adds the same default toString format to Scala Futures as 2…
@lrytz This contains the original version of the IntelliJ import commands without the improvements and fixes in the latest PR. Do you want to update this PR with the latest version or follow up with a manual update? Apart from that, LGTM |
i'll merge #5054 into 2.11.x and then append a commit here that merges the latest 2.11.x, OK? |
sounds good |
Update IntelliJ build for use with sbt
here's the log for the second part of the merge (commits pushed):
|
LGTM |
Follow-up for #5054