Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
In many portions of our build scripting, we use the invasive, modularity-breaking pattern of
subprojects {
configureSomething
}
This is particularly problematic when certain plugins or built-ins do not integrate well with each other, e.g, Gradle 5.2's java-platform needing to be applied before the java plugin.
As a result, within a single subproject, it is very difficult to know (without prior experience) how the subproject is configured.
This ticket is intended to be a "parent" ticket for jobs that fall into the following categories:
- Converting a plugin-script in gradle/ to a class extending Plugin<Project>.
- Moving a plugin to belong to buildSrc
- Converting invasive subproject [configuration] calls to be "opt-in" by the subprojects that require the configuration, such as the work done in
GEODE-6237.
