From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

```Caused by: org.gradle.internal.metaobject.AbstractDynamicObject$CustomMessageMissingMethodException: Could not find method dependencyManagement() for arguments [build_29ulvflvltljlgemnx04tmqjt$_run_closure13@8069462] on root project 'maxcodices' of type org.gradle.api.Project.
	at org.gradle.internal.metaobject.AbstractDynamicObject.methodMissingException(AbstractDynamicObject.java:182)
	at org.gradle.groovy.scripts.BasicScript$ScriptDynamicObject.methodMissingException(BasicScript.java:161)
	at org.gradle.internal.metaobject.AbstractDynamicObject.invokeMethod(AbstractDynamicObject.java:166)
	at org.gradle.groovy.scripts.BasicScript.invokeMethod(BasicScript.java:83)
	at build_29ulvflvltljlgemnx04tmqjt.run(/Users/JHe55/Workspace/nike/xxx/build.gradle:230)
	at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:91)
	... 128 more```

```dependencyManagement()```
is a method defined like it below

I have this after I upgrade springboot from 1.5.6.RELEASE to 2.1.3.RELEASE

So start with, I'd highly recommend to not use the spring boot dependencies plugin if it just for consuming BOMs, but instead use the built-in bom support with `platform(...)`.
That plugin is from a time where Gradle did not have BOM support and it has other features including questionable ports of imho broken-by-design Maven logic into Gradle.
If you don't need any of the additional features of that plugin, just kick it and use the built-in support instead.

Regarding the error, it means something is wrong inside the closure, but there is a bug that it is not displayed in a good way that is hopefully improved with Gradle 7.5. Currently when you get that error you need to comment out all lines within the closure and comment them in part by part to find the fault part, or in your case read the documenation of the plugin you are using to see what you do wrong.

This problem is one of the major reasons I greatly prefer the Kotlin DSL over the Groovy DSL, as you always get proper error messages, have immediately type-safe build scripts and an amazingly better IDE support including code completion.

Thanks for your message, Vampire. I’m finding solution