farmRunWar starts farm web-apps as WAR-files, in interactive and debug mode.


gradle farmRunWarDebug


  1. By default each farm web-app is compiled and assembled into WAR-file (if it’s not up-to-date).

  2. If farm configuration overrides inplace property for some web-apps to true, then each of these web-apps gets compiled without creating WAR-file (if it’s not up-to-date).

  3. Embedded servlet-container starts in separate java process against WAR-files (and, optionally, against compiled classes and their dependencies).
    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 the user keypress.

  6. When user presses any key (in the same terminal), servlet-container process shuts down.

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

  8. Gradle script continues normal execution of tasks.