Grails inline plugin modules have incorrect dependencies

I have several Grails application modules that depend upon custom Grails plugin modules that are specified via an inline plugin location in BuildConfig.groovy. The application dependencies seem to be resolved just fine, but the plugin modules have the incorrect dependencies: they seem to be given the dependencies of the projects depending on them, rather than having their own.

Example:

Modules: app, plugin-a, plugin-b

app depends on plugin-b (specified in BuildConfig.groovy as: grails.plugin.location.'plugin-b' = '../../plugins/pluginb' )
plugin-b depends on plugin-a (specified in BuildConfig.groovy as: grails.plugin.location.'plugin-a' = '../plugina' )

When I view the module dependencies for each module, I see the following:

- app:
- app-grailsPlugins
- plugin-a
- plugin-b

- plugin-b:
- app-grailsPlugins
- plugin-a

- plugin-a:
- app-grailsPlugins

Note that, instead of receiving their own '-grailsPlugins' dependencies, both plugins are given the grails dependencies of *app*, which depends on *them*! This is extremely frustrating. Additionally, if I remove the erroneous dependencies manually and save my settings, they are instantly re-added!

This is a near-blocker issue for anyone developing inline plugins alongside Grails applications.

---

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

Reproduce the app, plugin-a, and plugin-b setup using the inline grails.plugin.location entries in BuildConfig.groovy, then inspect how module dependencies are assigned. Done means each plugin receives its own -grailsPlugins dependencies rather than app's dependencies, and saving settings does not re-add the incorrect entries.

Written by the indexing model from the issue text.