Update gradle wrapper to 8.8

[8Keep]

Fix #2287

[stephengold]

Did you follow the documented update procedure?

[8Keep]

I didn't read the whole doc, most of it is irrelevant to us, but yeah that's pretty much what I did.

[stephengold]

Running gradlew wrapper --gradle-version=8.8 modifies the following files:

• gradle/wrapper/gradle-wrapper.jar
• gradle/wrapper/gradle-wrapper.properties
• gradlew
• gradlew.bat

Please include those change in this PR.

[stephengold]

I've reviewed the changes and don't see any problems. However, a change like this needs thorough testing more than it needs human review. I'm curious how much testing has been done so far:

• platforms (Android, Linux, macOS, and Windows)?
• tasks ("build", "clean", "dist", "install", "release", "mergedJavadoc", "mergedSource", "createZipDistribution", "copyLibs")?
• command-line options ("-PuseCommitHashAsVersionName", "-PbuildNativeProjects", "-PskipPrebuildLibraries")?

[stephengold]

@8Keep I remain curious.

[8Keep]

Let me try these later today. We should also run these in CI, I'm surprised that we don't already.

[8Keep]

@stephengold I've ran all the tasks you've sent, except release, because that doesn't exist. Unless you meant publish, which I can't finish due to not having a key. publishToMavenLocal does succeed.

copyLibs needed an update on line 117 of build.gradle. The thing is that according to some online sources, this was changed with gradle 7, so it may not have worked ever since the gradle 7 upgrade was done.

[stephengold]

Good progress, thank you.

I've ran all the tasks you've sent, except release, because that doesn't exist. Unless you meant publish, which I can't finish due to not having a key. publishToMavenLocal does succeed.

You're right: I was thinking of the publish tasks. Since "publishToMavenLocal" succeeded, there's a high probability that "publishMavenPublicationToSNAPSHOTRepository" and "publishMavenPublicationToOSSRHRepository" will also work.

I think this PR is ready for integration into the "master" branch. Do you agree?

[8Keep]

Yes, I agree. I want to do some followups, but I'll start these in separate prs:

1. Start running a java 21 build in CI
2. Start running more in CI to test all the tasks
3. Start getting rid of deprecated gradle features in the build, so the upgrade to gradle 9 goes smoothly

[8Keep]

It looks like publishing natives did fail once it was committed. Stephen, do you know what the implications of this error are:

https://github.com/jMonkeyEngine/jmonkeyengine/actions/runs/9820622481/job/27115496415#step:5:549

[stephengold]

I think it's related to a change at Sonatype. On 11 June, I got a cryptic e-mail from them about updating our plugin settings. Maybe those changes took effect sometime between 3 July and now?

I've generated Sonatype user tokens before, for my personal repos. I don't want to do it tonight when I'm tired. I'll investigate further tomorrow when I'm fresh.

[stephengold]

And now I see the CI for 5248fb0 succeeded, so perhaps it was just a transient network error. Let's wait and see whether it recurs.