build: unify Java 21 and Minecraft 1.21.10 - #8
Merged
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Unify this plugin’s build and loader metadata on Java 21 and Minecraft 1.21.10. Replace the private Spigot API jar with the provided
org.spigotmc:spigot-api:1.21.10-R0.1-SNAPSHOTdependency, setmaven.compiler.release=21andapi-version: 1.21.10, and use JDK 21 in build/release workflows. Remove the obsolete private API download and checksum.Validation:
mvn clean installpassed on JDK 21 with the coordinated Java 21 TFMC dependencies. All 37 Games tests passed. The resulting plugin jar contains only Java 21 class files (major 65) and declares API 1.21.10. No gameplay code or runtime configuration changed.Default dependency pins now use the published Java 21 releases: TLibs 1.1.1. Pinned local builds and CI therefore select the compatible dependency versions. Runtime smoke testing remains outstanding.