anchor.diff:  * link:[JetBrains's IDEA issue tracker],
   * link:[Google's Android Studio issue tracker].
   
  -Lastly, if you face problems with Gradle itself or with the Kotlin DSL, please open issues on the corresponding issue tracker:
  -
  -* link:{gradle-issues}[Gradle build tool issue tracker],
  -* link:{kotlin-dsl-issues}[Kotlin DSL issue tracker].
  +Lastly, if you face problems with Gradle itself or with the Kotlin DSL, please open issues on the link:{gradle-issues}[Gradle issue tracker].
   
   
   [[sec:scripts]]
  
positive.code: ** `$HOME/Library/Logs/gradle-kotlin-dsl` on Mac OS X
  ** `$HOME/.gradle-kotlin-dsl/logs` on Linux
  ** `$HOME/AppData/Local/gradle-kotlin-dsl/log` on Windows
  * Open an issue on the link:{kotlin-dsl-issues}[Kotlin DSL issue tracker], including as much detail as you can.
  
  From version 5.1 onwards, the log directory is cleaned up automatically.
  It is checked periodically (at most every 24 hours) and log files are deleted if they haven’t been used for 7 days.
  
negative.code: [[kotdsl:limitations]]
  == Limitations
  
  * The Kotlin DSL is link:https://github.com/gradle/kotlin-dsl/issues/902[known to be slower than the Groovy DSL] on first use, for example with clean checkouts or on ephemeral continuous integration agents.
  Changing something in the _buildSrc_ directory also has an impact as it invalidates build-script caching.
  The main reason for this is the slower script compilation for Kotlin DSL.
  * In IntelliJ IDEA, you must link:https://www.jetbrains.com/help/idea/gradle.html#gradle_import[import your project from the Gradle model] in order to get content assist and refactoring support for your Kotlin DSL build scripts.
  