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 May 9, 2015 at 6:41
-
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?– ziggystarCommented May 9, 2015 at 7:45
-
"What should I do?" not upgrading?– kiritsukuCommented May 9, 2015 at 8: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. SobralCommented May 9, 2015 at 12:24
-
1Android just switched from jdk6 to jdk7. Maintaining compatibility to over 1 billion active devices should be very relevant.– mucahoCommented May 10, 2015 at 12:09
Add a comment
|
1 Answer
Go work somewhere that has a future :)
Banging rocks together became obsolete, and so is Java 7.
answered May 9, 2015 at 7:53
-
4And indeed Java 7 is EOL as of April 2015. oracle.com/technetwork/java/eol-135779.html Commented May 9, 2015 at 8:11