...It wires common development workflows—starting an embedded container, serving an exploded webapp, or running a WAR—into familiar Gradle tasks. Configuration options let you set context paths, ports, and container versions, and tune features like reloading to shorten the edit-refresh loop. Because it integrates with Gradle’s war and dependency management, your servlet/JSP app can be built and exercised without installing Tomcat separately. Teams often use it to spin up local environments that mirror production packaging while keeping feedback fast. It reduces boilerplate scripts, centralizes environment settings in build.gradle, and makes Tomcat-based projects friendlier to new contributors.