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.

Sign up for GitHub

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

Jump to bottom

Bumping Java software version #660

Closed
Camotoy opened this issue Sep 23, 2021 · 10 comments
Closed

Bumping Java software version #660

Camotoy opened this issue Sep 23, 2021 · 10 comments

Comments

@Camotoy
Copy link
Member

Camotoy commented Sep 23, 2021

We'd like to bump the Java version used in MCProtocolLib and its dependencies to, ideally, Java 16 (to be in line with Java Edition itself). For users of this library, please let us know if that works for your setup or if it's inconvenient.
This was referenced Sep 23, 2021
Closed
Open
Open
@Newspicel
Copy link
Contributor

Newspicel commented Sep 26, 2021 •
edited
Loading

Personally, I would find this a good adjustment, which I would welcome very much.

@tycrek
Copy link
Contributor

tycrek commented Oct 20, 2021

Trying to switch all my/my orgs projects to Java 16, this would be a welcome change!

@kyngs
Copy link

kyngs commented Oct 23, 2021

If this is also a matter of: https://github.com/GeyserMC/PacketLib/; I need that to stay on Java 11, because I cannot find newer for ARMv6. So I have no issue with this bump, but I would be happy if you wouldn't bump PacketLib.

@MrZomka
Copy link

MrZomka commented Oct 23, 2021 •
edited
Loading

If this is also a matter of: https://github.com/GeyserMC/PacketLib/; I need that to stay on Java 11, because I cannot find newer for ARMv6. So I have no issue with this bump, but I would be happy if you wouldn't bump PacketLib.

Why not upgrade to better/newer hardware? Are you using an RPi Zero?

@SupremeMortal
Copy link
Member

SupremeMortal commented Oct 23, 2021 •
edited
Loading

I'm going to have to disagree with this. Bumping the Java version of a library for the sake of keeping it in line with Java Edition, but not using any of the new language features is not worth it. There may also be Android developers that use this library, and moving to Java 16 could make it incompatible.

@kyngs
Copy link

kyngs commented Oct 23, 2021

If this is also a matter of: https://github.com/GeyserMC/PacketLib/; I need that to stay on Java 11, because I cannot find newer for ARMv6. So I have no issue with this bump, but I would be happy if you wouldn't bump PacketLib.

Why not upgrade to better/newer hardware? Are you using an RPi Zero?

Yes, I use an RPi zero, even that is overkill for the task. I am glad that I even managed to find Java 11 for it.

@MatteCarra
Copy link
Contributor

I would find the change inconvenient for my usage. I have to agree with SupremeMortal.

@AlexProgrammerDE
Copy link
Contributor

image
It appears java 17 has been released for raspberry pi zeroes.

@Camotoy
Copy link
Member Author

Camotoy commented Dec 19, 2023

MCProtocolLib now uses Java 17.

@Camotoy Camotoy closed this as completed Dec 19, 2023
@Konicai
Copy link
Member

Konicai commented Dec 19, 2023

Release 1.20.4-1 targets Java 8. Anything forward requires Java 17.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@SupremeMortal @MatteCarra @Camotoy @MrZomka @tycrek @Newspicel @kyngs @AlexProgrammerDE @Konicai