I am developing a Gradle plugin to implement a custom build system. While it is currently functional, I am unsure whether I am adhering to the recommended practices or intended design patterns.
How it works:
A settings plugin is applied to configure the root project and its subprojects. The extension of this plugin specifies the root path to those subprojects, includes them in the root project, and applies a subproject
specific plugin to each of them. This secondary plugin adds a configuration to them so that these projects produce artifacts. Additionally, another project is configured by the settings plugin extension, which applies yet another plugin and adds a configuration to consume the artifacts produced by the other projects.
In this setup, the settings plugin orchestrates the entire project structure. It applies the Android Gradle plugin to projects that share artifacts, while the Java/Kotlin plugin is applied to the project consuming them.
However, for example, the design forces the Android plugin to be applied to all projects specified under the path in the settings plugin extension. What if I want to exclude a specific project under that path from this? It seems that this approach may not fully align with best practices or the intended design principles for Gradle plugins.