Skip to content

Multi-string dependency notation deprecated in Gradle 9.1.0 #233

@pkeller

Description

@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.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions