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

Gradle Community

&gt; Will `:modulea:moduleb` inherit plugins in the parent module `:modulea`?
If using the <https://docs.gradle.org/8.3/userguide/plugins.html#sec:plugins_block|plugins DSL>, then no, plugins aren't 'inherited' from parent modules. Plugins are only 'inherited' if using `subprojects {}`/`allprojects {}` (or some other funky way which Gradle probably allows), which is why `subprojects {}`/`allprojects {}` is discouraged.

hmm I wonder if the plugin I'm adding is walking the project tree and adding it's tasks in every project it finds below the project I applied the plugin to then

&gt; If so, how can I apply a plugin only if it hasn't already been applied
If using the plugins DSL, it's not possible to apply a plugin twice afaik

&gt; hmm I wonder if the plugin I'm adding is walking the project tree and adding it's tasks in every project it finds below the project I applied the plugin to then
that's possible :grimacing:. A lot of Gradle plugins aren't good citizens.

I'm using <https://github.com/Kotlin/binary-compatibility-validator> and I've added the plugin to modulea and when I add to moduleb it complains that the apiBuild/Check/Dump tasks have already been registered

yeah, BCV is not a good Gradle citizen <https://github.com/Kotlin/binary-compatibility-validator/issues/88>

that's why I re-wrote BCV to be compatible :grin:  <https://github.com/adamko-dev/kotlin-binary-compatibility-validator-mu>

how fortuitous this meeting has been :joy:

BCV-classic does have an option for excluding subprojects though, which isn't great, but it'll be a quick fix for your problem

```apiValidation {
    /**
     * Sub-projects that are excluded from API validation
     */
    ignoredProjects.addAll(listOf("benchmarks", "examples"))
}```

can I get a list of subprojects from a `project` instance at least?

trying to do this using conventions as best as i can

yeah, it's 'allowed' to use `subprojects` to get a list of subprojects

it's just not 'allowed' for one subproject to affect the configuration (e.g. apply a plugin, modify a task) of another subproject

cheers Adam, that little snippet seems to have been the duct tape being slapped right over my leak

&gt; If using the plugins DSL, it's not possible to apply a plugin twice afaik
Just scratch the first half of the sentence. :slightly_smiling_face:
Plugins are never applied multiple times, no matter how you apply them.
If you try to apply a plugin in any way that is already applied, it is a no-op.