anchor.diff:  [[sec:continuous_build]]
   == Continuous Build
   
  -Continuous Build allows you to automatically re-execute the requested tasks when task inputs change.
  +Continuous Build allows you to automatically re-execute the requested tasks when task inputs change. You can execute the build in this mode the `-t` or `--continuous` command-line option.
   
   For example, you can continuously run the `test` task and all dependent tasks by running:
   
  
positive.code: This flag also implies `--write-locks`.
  Learn more about this in <<dependency_locking.adoc#dependency-locking,dependency locking>>.
  
  `--no-rebuild`::
  Do not rebuild project dependencies.
  Useful for <<organizing_gradle_projects.adoc#sec:build_sources, debugging and fine-tuning `buildSrc`>>, but can lead to wrong results. Use with caution!
  
  
negative.code: `--refresh-dependencies`::
  Refresh the state of dependencies. Learn more about how to use this in the <<dynamic_versions.adoc#sec:controlling_dependency_caching_command_line,dependency management docs>>.
  
  `-m`, `--dry-run`::
  Run Gradle with all task actions disabled. Use this to show which task would have executed.
  
  `-t`, `--continuous`::
  Enables continuous build. Gradle does not exit and will re-execute tasks when task file inputs change. See <<#sec:continuous_build, Continuous Build section>> for more details.
  
  `--write-locks`::
  Indicates that all resolved configurations that are _lockable_ should have their lock state persisted.
  