Multi-string dependency notation deprecated in Gradle 9.1.0

[pkeller]

I am trying out Gradle 9.1.0 RC4, and getting a lot of warnings like this:

Declaring dependencies using multi-string notation has been deprecated. This will fail with an error in Gradle 10. Please use single-string notation instead: "org.slf4j:slf4j-api:2.0.17". Consult the upgrading guide for further information: https://docs.gradle.org/9.1.0-rc-4/userguide/upgrading_version_9.html#dependency_multi_string_notation

This comes from things like:

extraJavaModuleInfo {
    automaticModule("...")

and

javaModuleDependencies.gav("...")

I am using a version catalog for almost everything.

I can see that it could be a pain to sort this out, but something needs to be done to cater for Gradle 10. I'm not sure that I could contribute much to the code here, but I can probably help with testing using my current project.

[jjohannes]

Thank you for opening the issue and making us aware of the deprecation. I did not see that yet.

I think this is only an implementation detail of how the plugin internally constructs the dependencies. Should be straight forward to address.

[jjohannes]

Okay you were right. This is actually part of the "public API" of the plugin when using the version catalog.

I though it is simply changing a "Map of Strings" into a single "String". But if you have a rich version object, the version is not only a String. I have to investigate what the expected API to use is now. Maybe some version catalog specific dependency types (?).

[pkeller]

Thanks for picking this up so quickly. The org.gradlex Java module plugins are a lifesaver for me!

[jjohannes]

This is fixed in 1.10 which should be fully compatible with Gradle 9.0.0 and the upcoming 9.1.0 without causing deprecation warnings.

Please do not hesitate to give feedback if you encounter any issues @pkeller. Thanks again for reporting this early.