Skip to content

Commit

Permalink
Explain why the plugins get listed in the root project build script
Browse files Browse the repository at this point in the history
It dispels a bit of the magic that happens during a build. See the patch for
the thorough explanation.
  • Loading branch information
davidburstrom committed Jul 6, 2024
1 parent 373dae2 commit cde1607
Showing 1 changed file with 7 additions and 1 deletion.
8 changes: 7 additions & 1 deletion build.gradle.kts
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,13 @@ buildscript {

}

// Lists all plugins used throughout the project
/*
* By listing all the plugins used throughout all subprojects in the root project build script, it
* ensures that the build script classpath remains the same for all projects. This avoids potential
* problems with mismatching versions of transitive plugin dependencies. A subproject that applies
* an unlisted plugin will have that plugin and its dependencies _appended_ to the classpath, not
* replacing pre-existing dependencies.
*/
plugins {
alias(libs.plugins.android.application) apply false
alias(libs.plugins.android.library) apply false
Expand Down

0 comments on commit cde1607

Please sign in to comment.