Skip to content
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

Update required Java version to Java 17 #398

Open
1 task done
joshuasing opened this issue May 2, 2024 · 0 comments
Open
1 task done

Update required Java version to Java 17 #398

joshuasing opened this issue May 2, 2024 · 0 comments
Assignees
Labels
area: build This involves updating, adding or removing a build file status: breaking This involves breaking an existing API type: enhancement This is a feature request or a pull request that adds a feature
Milestone

Comments

@joshuasing
Copy link
Member

Confirmation

  • I have checked for similar issues.

Problem

The majority of platforms supported by Chameleon now require Java 17.
Additionally, Minecraft has required Java 17 since version 1.18 (released November 30, 2021).

Suggested solution

We should move to requiring Java 17 in Chameleon. We are already requiring Java 17 for building, as it is required by Paper, Sponge and soon Velocity (v3.3.0+).

As of May 3rd, 2024, data from bStats shows:

A plugin built with Chameleon, UltraStaffChatPro has similar statistics with even more adoption for Java 17 or newer:

From this data, we believe that upgrading to Java 17 will not affect the majority of people using software built with Chameleon. Additionally, most of these servers can upgrade to using Java 17 (except some legacy servers).

There are many major improvements between Java 11 and Java 17 that would be useful for use in Chameleon development, and would allow us to improve many parts of Chameleon. Additionally, new Java APIs would be available for use.

Additional information

No response

@joshuasing joshuasing added type: enhancement This is a feature request or a pull request that adds a feature area: build This involves updating, adding or removing a build file status: breaking This involves breaking an existing API labels May 2, 2024
@joshuasing joshuasing added this to the v0.20.0 milestone May 2, 2024
@LooFifteen LooFifteen pinned this issue May 2, 2024
@joshuasing joshuasing modified the milestones: v0.20.0, v0.21.0 May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: build This involves updating, adding or removing a build file status: breaking This involves breaking an existing API type: enhancement This is a feature request or a pull request that adds a feature
Projects
None yet
Development

No branches or pull requests

2 participants