anchor.diff:     Note that <<structuring_software_products_details.adoc#settings_convention_plugins,there are different strategies to avoid duplicating this information>> in each `settings.gradle(.kts)` of each of your components.
   4. _Declare platforms in a central place._
      Having a platform component as in the example is optional.
  -   You could do things without, e.g. by declaring <<dependency_constraints.adoc#dependency-constraints,dependency constraints>> directly in your convention plugins.
  -   However, <<platforms.adoc#sec:sharing-dep-versions-between-projects,platforms>> are a good option to have all the boundaries for the environment in which your software operates defined in a central place.
  +   You could do things without one of these, e.g. by declaring <<dependency_constraints.adoc#dependency-constraints,dependency constraints>> directly in your convention plugins.
  +   However, <<platforms.adoc#sec:sharing-dep-versions-between-projects,platforms>> are a good option to ensure all the boundaries for the environment in which your software operates defined in a central place.
  
positive.code: include::sample[dir="samples/build-organization/structuring-software-projects/kotlin",files="server-application/settings.gradle.kts"]
  ====
  
  We see that the `settings.gradle(.kts)` file only defines location for build logic components, other production code components and the inner structue of the component.
  Only the `build.gradle(.kts)` file in the `app` project then defines actual dependencies by applying a convention plugin and utilizing the _dependencies_ block.
  
  .Configuring type and dependencies of the `app` project inside the `server-application` component
  
negative.code: <1> That it is of type `groovy-gradle-plugin` or `kotlin-dsl` to allow convention plugins written in the corresponding DSL
  <2> It depends on our own `plugins-platform` from the `platforms` component
  <3> It depends on the `commons` project from `build-logic` to have access to our own commons convention plugin
  <4> It depends on the Spring Boot Gradle plugin from the Gradle Plugin Portal so that we may apply that plugin to our Spring Boot projects
  
  Now, we can write the convention plugin for Spring application like this:
  
  