Skip to content

JDK 17 blog post tweak #1770

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Mar 5, 2025
Merged

JDK 17 blog post tweak #1770

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0e0b2e8
tweaks to JDK 17 blog post
SethTisue Mar 5, 2025
64a6dd9
fix doubled .md extension
SethTisue Mar 5, 2025
6bcf920
add even more headers
SethTisue Mar 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 17 additions & 6 deletions _posts/2025-03-05-next-scala-lts-jdk.md.md → _posts/2025-03-05-next-scala-lts-jdk.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,19 @@ title: "JDK 17 will be the next minimum version required by Scala 3"
by: Tomasz Godzik, VirtusLab & Scala Core Team
---

We recently asked for community input about changing the JDK version used by the
Scala 3 compiler. We wanted to thank everyone for their input and announce the
We recently asked for community input on changing the JDK version used by the
Scala 3 compiler. We now thank everyone for their input and announce the
decision to switch to JDK 17 as the new minimum, starting with Scala 3.8 minor
and the subsequent new LTS which will mostly likely be Scala 3.9.

The discussion didn't uncover any compelling reason not to leave JDK 11 behind.
## Why drop 8?

Our reasoning for dropping 8 was presented in this [previous blog
post](https://www.scala-lang.org/blog/next-scala-lts.html).

## Why drop 11?

The discussion on whether to also drop 11 didn't uncover any compelling reason not to leave JDK 11 behind.
11 is now nearly as antiquated as 8, and moving from 11 to 17 is not normally considered a
difficult upgrade for users. 17 offers useful APIs and VM features. In the JVM
world, requiring 17+ is already a mainstream position and is becoming more so
Expand All @@ -19,12 +26,16 @@ we should take this chance to aid open-source maintainers by reducing the
testing and maintenance burden across the entire Scala 3 tooling and library
ecosystems as much as we reasonably can.

The open discussion that led to this decision can be found at the
[Scala contributors forum](https://contributors.scala-lang.org/t/next-scala-3-lts-version-will-increase-minimum-required-jdk-version).

## What about Scala 3.3 LTS?

This change only concerns future minor versions of Scala 3. In particular, the
Scala 3.3 LTS line is unaffected by this change. Scala 3.3.x releases will
continue for at least a year after the new LTS line begins.

## What about Scala 2?

There are no plans to change Scala 2’s JDK support. It will continue
being built using JDK 8, as before.

The open discussion that led to this decision can be found at the
[Scala contributors forum](https://contributors.scala-lang.org/t/next-scala-3-lts-version-will-increase-minimum-required-jdk-version).