This message was deleted.
# community-support
s
This message was deleted.
1
v
Remove the equals sign
❤️ 1
a
OMG!
😄 1
(here is the message with tons of dirty words)
Honestly, it's scary a little because you have never seen my code and instantly give me a solution!!
v
I just know how to interpret the error message. 🙂
Copy code
Could not set unknown property 'dependencyResolutionManagement' for settings
Means you have
dependencyResolutionManagement = ...
in your setting script and there is no valid syntax like that
And you are not the first using an equals sign in similar cases
a
It was still creepy 😄 thx a lot Mr. Nostradamus!
v
Well, you can alternatively assume I quickly hacked into your box and looked at your sources if that makes you feel more comfortable. 😄
a
Can you do it one more time and give a hint about it, please? 🙂
A problem occurred evaluating settings ‘service-name’.
> Could not find method dependencyResolutionManagement() for arguments [settings_5gr6kuukez26uvchtedabbm6q$_run_closure1@2612610] on settings ‘service-name’ of type org.gradle.initialization.DefaultSettings
e
that's an annoying category of error messages which can be difficult to debug even with the code available. but in short you need to make sure everything inside the
{}
is all valid - the error means there's something in the closure that Groovy decides makes it not applicable. (one massive benefit of using the Kotlin DSL is that this can't happen)
a
Is this type of error when you see smt like this in logs "hey, bro! here is an error, have a nice trip with investigation!"?
v
Actually as far as I remember in Gradle 7.5 they fixed something that hopefully reduces such error messages and shows something helpful instead. But yeah, these error messages are one of the reasons I exclusively use the Kotlin DSL nowadays wherever possible. If you want to stick with Groovy DSL, comment out the whole content of the closure and then comment it in part by part to find where you used wrong API.
a
I've commented absolutly all content inside:
Copy code
dependencyResolutionManagement {
    versionCatalogs {
        libs {
and it's failed with the same error. I try integrate
dependencyResolutionManagement
in a project which already works well with dependencies so I just try to improve dependency control here. Probably, smt in the build.gradel files affect
dependencyResolutionManagement
. Interesting.
v
No, you just didn't comment everything. If you would have commented everythign you would have found that it is the
versionCatalogs
.
This is new in 7.0
You can see this in the JavaDoc