Update to Gradle 7 #21
Comments
|
If you look closer, it's already been updated to Gradle 7 (at least rc-1, since that was the latest version of it at the time), it's just that it's on the indev (1.17) branch, not the 1.16 one. I do use the latest versions of Java as soon as they are released and because of that, Gradle will eventually be updated when I feel like working on it. Don't worry about Gradle versions, that will always be taken care of. Anyway, now to take care about one little problem: spamming this issue on every single Fabric mod repository that you have found. Please don't do that. If you really, really want to build mods on Java 16, patch it yourself, update gradle-properties.settings yourself, change the little 0.5/0.6 to 0.7 in the Loom version, and if processResources fails, then replace it with fabric-mod-template's version. I needed to build few mods on Java 16 myself and my solution for that wasn't complaining on all the repositories about that, I simply patched them myself. If it was something that really was a big issue for Java 16 (like Nashorn being removed in J15), I'd definitely try to do something about it, but a slightly outdated version of Gradle? Easily fixable, it can be dealt with it later. So, yeah, don't spam this on every single repository, Gradle 7 is pretty new anyway, so, patience is the key. |
ghost
closed this as 
I wasn't even aware this works like that... I was linking to the Sodium pr because there was everything explained... Now everybody is mad at me. Jelly even reported me, whatever this means, even tho I did no harm to her. Making a request to the devs to update the Gradle was the only way known to me to make it work with Java 16. If the devs don't want to update they can just close the issue and forget about it. Why are they so angry 😞 |
|
@RDKRACZ they are upset because it is basically spam for something that most people don't ever use lol. I absolutely understand you had good intentions and was trying to help everyone. But it is always a better idea to ask an experience modder about these kinds of stuff first as they may have workarounds like joaoh1 mentioned that you can do. It is a lot better than poking a massive ton of people to do an update for something non-critical. If something like this were to become an actual issue and affect a large portion of mods, Fabric toolchain has ways of notifying most modders or adding workarounds into their own toolchain for everyone to benefit from. There's no need to be the messenger yourself. Just sit back, relax, and let Fabric toolchain handle these kinds of stuff. Hopefully this makes sense! |
(and Loom to the 0.7 snapshot) to be able to build with Java 16.
Take a look at CaffeineMC/sodium-fabric#630
The text was updated successfully, but these errors were encountered: