Conversation
- Use Java 25 for CIs - Dropped now-unneeded remapping/reobfuscation configurations and pre-compiled script plugin - Copied all previously-shared classes into Spigot-specific packaging - This will potentially result in duplicated code maintenance, but makes it much easier to catch new server implementation differences at compile time. - Repackage Spigot internals
|
Looks like the problem with the build is actually the |
# Conflicts: # gradle/libs.versions.toml
|
Currently only Paper 26.1.1 and Spigot 26.1(.1) are supported and nothing has been tested. I'll get to re-adding backwards compatibility later, I'm done for the day. I fought with Gradle for a couple hours to figure out how to force it to allow dependency resolution despite "mismatching" capabilities for a while. The internal modules' inheritance is basically backwards, and I didn't know enough about Gradle or think it through far enough when I was doing the initial setup for v5. With the advent of Mojang actually versioning things again, I will likely return to dropping old versions, particularly with versions' ages showing pretty clearly in version numbers. I'm thinking a rolling year window for support. If anyone has strong opinions on the matter, please let me know. |
As always, please exercise caution when using development builds (assuming the CI doesn't fail, it being set to Java 21 right now).
TODO: