gradle farmStartWar
farmStartWarDebug starts farm web-apps as WAR-files in debug mode.
By default each farm web-app is compiled and assembled into WAR-file (if it’s not up-to-date).
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).
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.
Upon resume, servlet-container process starts listening for HTTP-requests on port (default 8080).
Gretty waits for servlet-container process to complete.
Gradle script continues normal execution of tasks.
Note
|
this task does not stop Jetty. It is assumed that another gradle process stops it, supposedly gradle farmStop. |
See also: farmStop task and farmRestart task.