anchor.diff:  If the build is being executed via the Tooling API, the build can be cancelled using the Tooling API's cancellation mechanism.
   
   [[continuous_build_limitations]]
  -=== Limitations and quirks
  -
  -There are several issues to be aware with the current implementation of continuous build.
  -These are likely to be addressed in future Gradle releases.
  +=== Limitations
  +
  +Under some circumstances continuous build will not detect changes to inputs.
  +
  +[[sec:continuous_build_missing_files]]
  +==== Adding new root input directories
  +
  +Sometimes, adding root input directories does not trigger a build, due to the way file system watching works.
  +For example, when adding the `src/main/java` directory, Gradle may not trigger a build.
  +Similarly, if the input is a <<working_with_files.adoc#filtering_files,filtered file tree>>, Gradle may not detect the addition of the first file matching the filter.
  +
  +[[sec:continuous_build_untracked]]
  +==== Inputs of untracked tasks
  +
  +Gradle will only watch for changes of inputs of tasks if it captures their state.
  +That means changes to the inputs of <<more_about_tasks.adoc#sec:disable-state-tracking,untracked tasks>> or tasks that have no outputs will not trigger a build.
  +
  +[[sec:continuous_build_project_dir]]
  +==== Changes to files outside of project directories
  +
  +Gradle only watches for changes to files inside the project directory.
  +Changes to files outside of the project directory will go undetected and not trigger a build.
   
   [[sec:build_cycles]]
   ==== Build cycles
  
positive.code: This means that unrelated changes (such as changes to build scripts) will not trigger a rebuild.
  In order to incorporate build logic changes, the continuous build must be restarted manually.
  
  === Terminating Continuous Build
  
  If Gradle is attached to an interactive input source, such as a terminal, the continuous build can be exited by pressing `CTRL-D` (On Microsoft Windows, it is required to also press `ENTER` or `RETURN` after `CTRL-D`).
  
negative.code: In some cases, it may be obvious (e.g., a Java file is compiled with `compileJava`).
  In other cases, you can use `--info` logging to find the task that is out-of-date due to the identified files.
  
  [[sec:changes_to_symbolic_links]]
  ==== Changes to symbolic links
  
  In general, Gradle will not detect changes to symbolic links or to files in the target of symbolic links.
  
  [[sec:changes_to_build_logic_are_not_considered]]
  ==== Changes to build logic are not considered
  