anchor.diff:  <1> Declaratively request the `com.android.application` plugin
   <2> Configure the `android` extension using Kotlin DSL type safe accessor
   
  -See the link:{user-manual}plugins.html#sec:plugin_management[Plugin Management] section of the Gradle user manual for more information.
  +See the <<plugins#sec:plugin_management, Plugin Management>> section of the Gradle user manual for more information.
   
   The same approach can be used to resolve plugins from composite builds, which link:https://github.com/gradle/gradle/issues/2528[do not expose plugin markers] yet.
   Simply map the plugin ID to the corresponding artifact coordinates as shown in the Android samples above.
  
positive.code: 
  To use the Kotlin DSL, simply name your files `build.gradle.kts` instead of `build.gradle`.
  
  The link:{user-manual}build_lifecycle.html#sec:settings_file[settings file], `settings.gradle`, can also be renamed `settings.gradle.kts`.
  
  In a multi-project build, you can have some modules using the Groovy DSL (with `build.gradle`) and others using the Kotlin DSL (with `build.gradle.kts`).
  
  On top of that, apply the following conventions for better IDE support:
  
  * Name scripts that are applied to `Settings` according to the pattern `*.settings.gradle.kts`,
  * Name link:{user-manual}init_scripts.html[init scripts] according to the pattern `*.init.gradle.kts`.
  
  [TIP]
  .Precompiled script plugins
  
negative.code: <4> Configure the `blockName` property, maps to a `Closure` taking method invocation
  <5> Invoke `another` method taking named arguments, maps to a Groovy named arguments `Map<String, ?>` taking method invocation
  
  The link:{kotlin-dsl-samples}maven-plugin[maven-plugin] sample demonstrates the use of the `withGroovyBuilder()` utility extensions for configuring the `uploadArchives` task to <<maven_plugin#sec:deploying_to_a_maven_repository, deploy to a Maven repository>> with a custom POM using Gradle's core <<maven_plugin#, Maven Plugin>>.
  Note that the recommended <<publishing_maven#, Maven Publish Plugin>> provides a type-safe and Kotlin-friendly DSL that allows you to easily do <<publishing_maven#sec:modifying_the_generated_pom, the same and more>> without resorting to `withGroovyBuilder()`.
  
  === Using a Groovy script
  
  