Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

[fronobulax]

Not sure best place to discuss.

When I build locally I get the above message at the end of the build. I don't recall how long I have been getting it because I usually build from a batch file the closes the command window so I have to be watching closely to see it. Is this something other folks are seeing or is it an artifact of my batch file on Windows? If it is not just me is anyone looking at Gradle 9 and what we might need to change?

Thanks.

 

[xKiv]

Same on linux, always.

$ ./gradlew --warning-mode all
Starting a Gradle Daemon (subsequent builds will be faster)

> Configure project :
The CopyProcessingSpec.setFileMode(Integer) method has been deprecated. This is scheduled to be removed in Gradle 9.0. Please use the filePermissions(Action) method instead. Consult the upgrading guide for further information: https://docs.gradle.org/8.8/userguide/upgrading_version_8.html#unix_file_permissions_deprecated

That's the only one it's telling me.
Doesn't even say where, and there doesn't seem to be anything about setFileMode in the source, so probably an outdated plugin?

 

[heeheehee]

Doesn't even say where, and there doesn't seem to be anything about setFileMode in the source, so probably an outdated plugin?

Looks like the shadow plugin.

Gradle Warning: CopyProcessingSpec.setFileMode(Integer) method has been deprecated · Issue #924 · GradleUp/shadow

including the plugin on gradle 8.8 results in the following message printed: The CopyProcessingSpec.setFileMode(Integer) method has been deprecated. This is scheduled to be removed in Gradle 9.0. P...

github.com

 

[heeheehee]

> NOTE: This plugin changed the core maintainer and has new coordinates:https://plugins.gradle.org/plugin/com.gradleup.shadow

Gradle - Plugin: com.github.johnrengelman.shadow

plugins.gradle.org

I'll send a PR in a bit.

 

[heeheehee]

Update dependencies. by heeheehee-kolmafia · Pull Request #2413 · kolmafia/kolmafia

Most of these are only minor version bumps, but there were a handful of major version changes. Most notably: the maintainer for shadow has changed, along with the package naming. Hamcrest 3.0 looks...

github.com

 

[fronobulax]

I have the update. Just tried spotless apply and got

> Task :spotlessGroovyGradle
Missing required bundle org.eclipse.jdt.debug needed by [org.eclipse.jdt.launching]
Recommend setting osgi.configuration.area to a directory, getDataFile will return null
Starting Groovy-Eclipse compiler resolver. Specified compiler level: unspecified
124 org.codehaus.groovy_5.0.0.v202309291934-e2309 RESOLVED

Doesn't seem to prevent anything but...

 

[heeheehee]

I saw that too. It's probably related to at least one of the dependencies I bumped.

When I tried upgrading spotless, that yielded some actual diffs, so I held off for the time being. I'll look into it some more.

 

[heeheehee]

I see the same error on r28030 (i.e. before my dependency bump). It seems nominally benign, although I believe it's tied to the greclipse() line in the spotless stanza.

 

[fronobulax]

I see the same error on r28030 (i.e. before my dependency bump). It seems nominally benign, although I believe it's tied to the greclipse() line in the spotless stanza.

I don't recall seeing it before but then I probably had not run spotless in several weeks. Finally got the IDE to format correctly and not comitting anything.