Repository navigation
Increasing minimum supported JDK (and dropping support for JDK 11) #1159
Description
Activity
- pinned this issue
on Sep 11, 2024 Doesn't the runtime version determine the source code version at the moment? Or does GJF support a
--source 11option? 🤔Afaict it determines what can be parsed but not how it'll be formatted.
Reacted by Christian Stein and Liam Miller-CushonAfaict it determines what can be parsed but not how it'll be formatted.
Right, it'll parse at whatever the newest language level supported by the runtime is, and shouldn't affect formatting. Newer source versions are usually a superset of older ones, but there are some occasional breaking changes like new reserved identifiers, #975 is a related FR about making the source version g-j-f parses at configurable.
Reacted by Thomas BroyerI just pushed another release, and am planning to update the minimum supported JDK to 17 for the next release after that one: https://github.com/google/google-java-format/releases/tag/v1.24.0
Reacted by Stephan Schroevers and Christian Stein- added 5 commits that reference this issue
on Oct 4, 2024 - added 2 commits that reference this issue
on Nov 18, 2024 I pushed 1.25.0, which raises the minimum supported JDK to JDK 17: https://github.com/google/google-java-format/releases/tag/v1.25.0
(I previously mistakenly updated the release notes for 1.24.0, I have finished publishing the 1.25.0 release and restored the 1.24.0 relnotes, sorry for the mixup.)
Reacted by Stephan Schroevers- unpinned this issue
on Nov 23, 2024
Following the example of google/error-prone#3803, we're considering removing support for running google-java-format on JDK 11. The new minimum supported JDK would be JDK 17 (the next LTS release after 11).
google-java-format would still fully support formatting earlier source code versions, it would just require running the tool on JDK 17 or later.