Closed as not planned
Description
I have a multi-module project configuration error when I want to apply a plugin to individual modules.
Why not just do it at the level of the entire project?
The project contains many modules, and the dump API is needed by only a small part of them, and even in the distant future it will be a small proportion, so I would not like to apply the plugin to modules that do not require it.
However, now, if you do this, such an error occurs:
A problem occurred evaluating project ':module_name'.
> Failed to apply plugin 'org.jetbrains.kotlinx.binary-compatibility-validator'.
> Cannot add a configuration with name 'bcv-rt-jvm-cp' as a configuration with that name already exists.
I found a workaround for this behavior:
project.afterEvaluate {
configurations.findByName("bcv-rt-jvm-cp")
?: project.apply(plugin = "org.jetbrains.kotlinx.binary-compatibility-validator")
}
But it would be cool for this to be supported, including out of the box, and not have to create strange workarounds.
Metadata
Metadata
Assignees
Labels
No labels