farmStartDebug starts farm web-apps inplace, in debug mode.


gradle farmStartDebug


  1. Each farm web-app gets compiled (if it’s not up-to-date).

  2. If farm configuration overrides inplace property for some web-apps to false, then each of these web-apps is assembled into WAR-file (if it’s not up-to-date).

  3. Embedded servlet-container starts in separate java process against compiled classes and their dependencies (and, optionally, WAR-files).
    important: Upon start, the process is in suspended-mode and listens for debugger commands on port 5005.

  4. Upon resume, servlet-container process starts listening for HTTP-requests on port (default 8080).

  5. Gretty waits for servlet-container process to complete.

  6. Gradle script continues normal execution of tasks.

by default this task does not depend on any "war" tasks. It’s only when you override inplace property to false are some projects compiled to WAR-files and farmRun depends on respective "war" tasks.
this task does not stop Jetty. It is assumed that another gradle process stops it, supposedly gradle farmStop.