Grails: "Incompatible type assignments" inspection warning for valid dependency specification code in BuildConfig.groovy

In `BuildConfig.groovy`, valid dependency specification triggers "Incompatible type assignments" warning. For example, in the `BuildConfig.groovy` of a plugin just generated with "`grails create-plugin`" command (grails 2.3.11), there is a declaration
```
build(":release:3.0.1", ":rest-client-builder:1.0.3") {
export = false
}
```
Idea complains that "build cannot be applied to (java.lang.String, java.lang.String, groovy.lang.Closure<java.lang.Boolean>)" although declaration is perfectly valid.

---

*Imported from [IDEA-133340](https://youtrack.jetbrains.com/issue/IDEA-133340) · Type: Bug · Votes: 0*
*Comments, attachments, dates and reporter are not part of the export — follow the link above for the full history.*

Reproduce the warning in a plugin-generated BuildConfig.groovy from Grails 2.3.11, using the build dependency declaration shown in the issue. Trace how the IntelliJ inspection resolves build with two dependency strings and a closure, then verify that the valid declaration no longer reports an incompatible type assignment while its behavior remains unchanged.

Written by the indexing model from the issue text.