Use Java 21 on Jitpack

[PimvanderLoos]

Description:

Updated the Java version used by JitPack from 17 to 21. The reason for this is:

1. This fixes compilation on JitPack. The build fails while trying to compile towny-paper-provider due to class file has wrong version 65.0, should be 61.0. JitPack shows that the status is ok, but it only actually publishes artifacts for towny-folia-provider, towny-base-providers, and towny-parent. Crucially, no artifact for the towny module is published, as you can see in the logs for 0.101.1.1.
2. This brings it in line with the version used by the Actions workflow to compile the project.

---

New Nodes/Commands/ConfigOptions:

---

Relevant Towny Issue ticket:

---

• I have tested this pull request for defects on a server.

By making this pull request, I represent that I have the right to waive copyright and related rights to my contribution, and agree that all copyright and related rights in my contributions are waived, and I acknowledge that the TownyAdvanced organization has the copyright to use and modify my contribution under the Towny License for perpetuity.

[LlmDl]

Towny is currently set to use Java 17, in order to make things easier for servers still using MC 1.19.

I'm not sure what the correct move is here, whether to bump is just for jitpack or to leave it be.

[PimvanderLoos]

Hey, thanks for taking a look at this PR!

You don't need to bump it for JitPack. It just needs a >21 JVM to compile it, as the paper module is compiled against class file 65 (Java 21) and thus needs to be able to read/parse/whatever-it's-called it.

Towny will still target Java 17; the files will be compiled to class file 61 (Java 17). I verified this with the jar compiled by JitPack from my branch: https://jitpack.io/com/github/PimvanderLoos/Towny/towny/master-fe30be79ec-1/towny-master-fe30be79ec-1.jar.
As such, this has no impact on compatibility and can still be used with Java 17 on MC 1.19.

[LlmDl]

Ah right, thank you.

…

On Mon, Jan 27, 2025, 4:22 PM Pim van der Loos ***@***.***> wrote: Hey, thanks for taking a look at this PR! You don't need to bump it for JitPack. It just needs a >21 JVM to compile it, as the paper module is compiled against class file 65 (Java 21) and thus needs to be able to read/parse/whatever-it's-called it. Towny will still target Java 17; the files will be compiled to class file 61 (Java 17). I verified this with the jar compiled by JitPack from my branch: https://jitpack.io/com/github/PimvanderLoos/Towny/towny/master-fe30be79ec-1/towny-master-fe30be79ec-1.jar . As such, this has no impact on compatibility and can still be used with Java 17 on MC 1.19. — Reply to this email directly, view it on GitHub <#7746 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGWZDCRGFSLAA7CJAXHSTL2M2WTPAVCNFSM6AAAAABV42LEZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJXGAZDEMBSGQ> . You are receiving this because you commented.Message ID: ***@***.***>