anchor.diff:  
   You can also replace much of Gradle’s logging with your own by registering various event listeners. One example of a <<sec:changing_what_gradle_logs,custom event logger is explained in the logging documentation>>. You can also <<sec:external_tools,control logging from external tools>>, making them more verbose in order to debug their execution.
   
  -**Note:** Additional logs from the <<gradle_daemon,Gradle Daemon>> can be found under `GRADLE_USER_HOME/daemon/<gradle-version>/`.
  +[NOTE]
  +Additional logs from the <<gradle_daemon,Gradle Daemon>> can be found under `GRADLE_USER_HOME/daemon/<gradle-version>/`.
   
   ==== Task executed when it should have been UP-TO-DATE
   
  
positive.code: </figure>
  ++++
  
  **NOTE:** You must either stop running Gradle Daemons or run with `--no-daemon` when using debug mode.
  
  ==== Adding and changing logging
  
  
negative.code: ❯ gradle --version
  
  -----------------------------------------------------------
  Gradle 4.6
  ------------------------------------------------------------
  
  Build time:   2018-02-21 15:28:42 UTC
  Revision:     819e0059da49f469d3e9b2896dc4e72537c4847d
  
  Groovy:       2.4.12
  Ant:          Apache Ant(TM) version 1.9.9 compiled on February 2 2017
  