|
| 1 | +--- |
| 2 | +category: blog |
| 3 | +permalink: /news/next-scala-lts-jdk.html |
| 4 | +title: "JDK 17 will be the next minimum version required by Scala 3" |
| 5 | +by: Tomasz Godzik, VirtusLab & Scala Core Team |
| 6 | +--- |
| 7 | + |
| 8 | +We recently asked for community input about changing the JDK version used by the |
| 9 | +Scala 3 compiler. We wanted to thank everyone for their input and announce the |
| 10 | +decision to switch to JDK 17 as the new minimum, starting with Scala 3.8 minor |
| 11 | +and the subsequent new LTS which will mostly likely be Scala 3.9. |
| 12 | + |
| 13 | +The discussion didn't uncover any compelling reason not to leave JDK 11 behind. |
| 14 | +11 is now nearly as antiquated as 8, and moving from 11 to 17 is not normally considered a |
| 15 | +difficult upgrade for users. 17 offers useful APIs and VM features. In the JVM |
| 16 | +world, requiring 17+ is already a mainstream position and is becoming more so |
| 17 | +with every passing month. Also, we increase Scala's minimum so rarely, we feel |
| 18 | +we should take this chance to aid open-source maintainers by reducing the |
| 19 | +testing and maintenance burden across the entire Scala 3 tooling and library |
| 20 | +ecosystems as much as we reasonably can. |
| 21 | + |
| 22 | +This change only concerns future minor versions of Scala 3. In particular, the |
| 23 | +Scala 3.3 LTS line is unaffected by this change. Scala 3.3.x releases will |
| 24 | +continue for at least a year after the new LTS line begins. |
| 25 | + |
| 26 | +There are no plans to change Scala 2’s JDK support. It will continue |
| 27 | +being built using JDK 8, as before. |
| 28 | + |
| 29 | +The open discussion that led to this decision can be found at the |
| 30 | +[Scala contributors forum](https://contributors.scala-lang.org/t/next-scala-3-lts-version-will-increase-minimum-required-jdk-version). |
0 commit comments