Skip to content

Recommend java 16 for 1.17 - #234

Open
CelDaemon wants to merge 1 commit into
FabricMC:mainfrom
CelDaemon:mc1.17-jdk
Open

CelDaemon wants to merge 1 commit into
FabricMC:mainfrom
CelDaemon:mc1.17-jdk

Conversation

@CelDaemon

Copy link
Copy Markdown
Contributor

Versions 1.17 and 1.17.1 used java 16, as shown in the manifest:

https://piston-meta.mojang.com/v1/packages/0d9ace8a2ecfd1f4c782786f4b985a499240ff12/1.17.json

"javaVersion": {
  "component": "java-runtime-alpha",
  "majorVersion": 16
},

@Jab125

Jab125 commented Sep 22, 2026 •

Copy link
Copy Markdown

Java 16 though, isn't LTS, Java 17 is an LTS release, Java 16 stopped receiving support a long time ago

@CelDaemon

Copy link
Copy Markdown
Contributor Author

Hmmm that is fair. But then the question is, do we want to be accurate to what mc uses, or follow LTS releases?

@sylv256

sylv256 commented Sep 22, 2026

Copy link
Copy Markdown
Member

If Minecraft still uses it when selecting that version, it would be best to use that since Fabric should be as neutral as possible imo.

@modmuss50

Copy link
Copy Markdown
Member

This is something that was discussed previously, there was no reason to recommend Java 16 over 17. You can build mods using 17 that still run just fine on 16.

@CelDaemon

CelDaemon commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor Author

Ah, I didn't see the previous discussion about this, sorry for that.

You can build mods using 17 that still run just fine on 16.

They have different class file versions though. Wouldn't you need to configure the build system with the proper java version to get it to run?

If we don't want to link to an older JDK, it might make sense to have a separate table for the actual java versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants