feat: use java 17 for api components#1650
Merged
0utplay merged 7 commits intoCloudNetService:nightlyfrom Jun 22, 2025
Merged
Conversation
derklaro
force-pushed
the
feat/api-on-java-21
branch
from
8bce9fe to
020c00b
Compare
derklaro
added
v: 4.X
This change adds a new version bundle that excludes the `dev.derklaro.aerogel:aerogel-scoped-value-context-scope` dependency. This dependency cannot be used in API modules, because those do not use Java 24.
derklaro
force-pushed
the
feat/api-on-java-21
branch
from
020c00b to
0b3cb6f
Compare
0utplay
changed the title
0utplay
previously approved these changes
Jun 22, 2025
derklaro
reviewed
Jun 22, 2025
0utplay
approved these changes
Jun 22, 2025
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
3 participants
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.
Motivation
We want to ease the development of modules and plugins that interface with CloudNet. Currently CloudNet requires Java 24 in its runtime and consequently its API.
The API has already been extracted from the implementation and thus efforts to relax the Java version constraints can be realised.
Modification
With this PR the API components relax their Java version requirements from Java 24 to Java 17.
Result
The API components can now be used in projects that do not work or want to constraint themselves to Java 24.
Other context
See this very small exchange on Discord: https://discord.com/channels/325362837184577536/818777626663321671/1380941029741694986.
These changes built upon #1566.