The release of Scala 2.12 Milestone 1 indicates it requires Java 1.8. What should Scala users who are not able to go to Java 1.8 at this moment plan to do?
Asked
Active
Viewed 409 times
7
-
2Run around in circles and panic! Seriously, I cannot imagine an alternative to the obvious answer of staying with 2.11. Backport Scala 2.12 to Java 7? – ziggystar May 09 '15 at 07:45
-
"What should I do?" not upgrading? – kiritsuku May 09 '15 at 08:11
-
6Guys, I happen to know the answer to this question. I just wanted to give someone else the chance to answer first. Regardless, here's the thing: stack overflow was MADE for people to get answers to actual problems. Deriding a question because you don't know the answer to it is the worst possible sin one could make here. – Daniel C. Sobral May 09 '15 at 12:24
-
1Android [just switched from jdk6 to jdk7](http://stackoverflow.com/a/30015557/3041008). Maintaining compatibility to over [1 billion active devices](http://thenextweb.com/google/2014/06/25/google-activations-io-2014/) should be very relevant. – mucaho May 10 '15 at 12:09
1 Answers
7
Go work somewhere that has a future :)
Banging rocks together became obsolete, and so is Java 7.
Mike Slinn
- 7,705
- 5
- 51
- 85
-
4And indeed Java 7 is EOL as of April 2015. http://www.oracle.com/technetwork/java/eol-135779.html – Matthew Farwell May 09 '15 at 08:11