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

Java 8 end-of-life #1321

Closed
bensku opened this issue Jun 18, 2018 · 9 comments
Closed

Java 8 end-of-life #1321

bensku opened this issue Jun 18, 2018 · 9 comments
Labels
completed The issue has been fully resolved and the change will be in the next Skript update. core task Tasks that may be handled only by the core developer team. enhancement Feature request, an issue about something that could be improved, or a PR improving something. priority: medium Issues that are detrimental to user experience (prohibitive bugs or lack of useful implementation).
Milestone

Comments

@bensku
Copy link
Member

bensku commented Jun 18, 2018

I do not like removing or deprecating major features (cough Minecraft 1.9 cough) without some warning time. So, here it goes:

Java 8 is end-of-life in January 2019. After that, most users will not get bug fixes, security patches or any other updates from Oracle. They should migrate to either Java 10 or (preferably) 11.

For Skript, this means that releases made after January may not support Java 8. After all, running a server on top of unsupported, insecure, Java version would be a bad idea.

Edit: Corrected a few dates. Note that these apply only to Oracle JRE; most Linux distros ship OpenJDK which might have different support lifecycle.

@bensku bensku added the documentation Related to Skript's official documentation. label Jun 18, 2018
@28andrew
Copy link
Contributor

Seems like Java 8 is getting LTS updates until 2019. I'm down for migrating Skript to Java 10 or 11. Hopefully Mojang makes Minecraft Java Edition use Java 10+ by then so server hosting providers are forced to update.

@bensku
Copy link
Member Author

bensku commented Jun 19, 2018

Seems that I looked at outdated roadmap. Java 8 is getting a few more months of updates than I thought. I'll update the original post.

Note that it seems unclear if some random OpenJDK builds you have will get security fixes on Java 8 after Java 11 is released. Be sure to check it if you're not running Oracle's build.

@Matsjee I was a couple of months early with the date. It is also not likely that we'll start building for Java 11 immediately. Still, I see no reason to support insecure software; we'll eventually move on, after Java 8 is EOL.

@Nicofisi
Copy link
Member

Does Spigot work fine on Java 10 right now? Just curious

@bensku
Copy link
Member Author

bensku commented Jun 19, 2018

I have not noticed any issues. It is possible that some plugins do not work well. Also, Minecraft client doesn't really work with Java 9+ as far as I know. However, Mojang usually ships Java for players, so that is their problem.

@AyhamAl-Ali
Copy link
Member

AyhamAl-Ali commented Jul 27, 2021

End of life of this issue maybe? Since Skript requires Java 16 for compilation now but runs on older Java versions

@TPGamesNL
Copy link
Member

Skript only requires Java 16 for compilation, runtime still allows Java 8 therefore we cannot use any features from Java 9+

@TPGamesNL TPGamesNL reopened this Feb 24, 2022
@TheLimeGlass
Copy link
Collaborator

@TPGamesNL I don't think we need to have this as an active issue? What is it representing, we recommend Java 12+ more or so Java 17+ but we still compile to Java 8 as Skript still supports 1.13-1.16 which can run on Java 8.

@TPGamesNL
Copy link
Member

The issue is about dropping support for Java 8 (or switching to a higher target Java version), which is still a possibility even if we keep supporting 1.13 - 1.16, because 1.13 - 1.16 runs on Java 11 as well.

@TheLimeGlass TheLimeGlass added enhancement Feature request, an issue about something that could be improved, or a PR improving something. priority: medium Issues that are detrimental to user experience (prohibitive bugs or lack of useful implementation). core task Tasks that may be handled only by the core developer team. and removed documentation Related to Skript's official documentation. labels Mar 25, 2023
@TheLimeGlass TheLimeGlass added this to the v3.0 milestone May 5, 2023
@Moderocky
Copy link
Member

Java 8 support will be dropped in favour of Java 11 as of Skript 2.9.
As Java 11 is also past its end-of-life, we will be dropping that in favour of Java 17 in future.

@Moderocky Moderocky added completed The issue has been fully resolved and the change will be in the next Skript update. PR available Issues which have a yet-to-be merged PR resolving it labels Apr 12, 2024
@APickledWalrus APickledWalrus removed the PR available Issues which have a yet-to-be merged PR resolving it label Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
completed The issue has been fully resolved and the change will be in the next Skript update. core task Tasks that may be handled only by the core developer team. enhancement Feature request, an issue about something that could be improved, or a PR improving something. priority: medium Issues that are detrimental to user experience (prohibitive bugs or lack of useful implementation).
Projects
None yet
Development

No branches or pull requests

8 participants