I fear I may be misusing multi-project builds, but I currently have the following structure for a Java project:
/ build.gradle core/ build.gradle plugins/ build.gradle plugin a/ plugin b/
I have bundled the plugins into a grouping ‘plugins’ project solely because all plugins share certain build dependencies and tasks. There is no Java code in this project, and nor should there be any other artifacts.
The problem with this is, of course, that ‘plugins’ is treated by Gradle as a project in its own right rather than a grouping mechanism. This means that, say, if the ‘jar’ target is run for the whole multi-project, a skeletal ‘plugins.jar’ is created.
This is liveable, just a bit confusing.
Is there a recommended way to have shared configuration for a selected group of sub-projects? Are n-deep projects advised against?