-
Notifications
You must be signed in to change notification settings - Fork 326
docs: Announce core decision about JDK #1763
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
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
d596c2a
docs: Announce core decision about JDK
tgodzik 901f12b
Update _posts/2025-03-05-next-scala-lts-jdk.md.md
SethTisue fc5489f
Update _posts/2025-03-05-next-scala-lts-jdk.md.md
SethTisue 9970fb9
Update _posts/2025-03-05-next-scala-lts-jdk.md.md
SethTisue f05d62d
Update _posts/2025-03-05-next-scala-lts-jdk.md.md
SethTisue af973cc
review feedback
SethTisue 6aea853
put in correct category
SethTisue File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
--- | ||
category: blog | ||
permalink: /news/next-scala-lts-jdk.html | ||
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 | ||
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. | ||
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 | ||
with every passing month. Also, we increase Scala's minimum so rarely, we feel | ||
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. | ||
|
||
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. | ||
|
||
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). |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.