The path to the Tomcat context XML file (defaults to src/main/webapp/META-INF/context.xml for tomcatRun,ĭefaults to META-INF/context.xml within the WAR for tomcatRunWar). Specifies the character encoding used to decode the URI bytes by the HTTP If it doesn't get defined an instance of .DefaultServlet and .JspServlet will be set up.ĭefines additional runtime JARs or directories that are not provided by the The URL context path your web application will be registered under (defaults
You can set the following optional task properties: The web application will be accessible under the context path sample-app. ToĮnable SSL we set the property enableSSL to true.
JREBEL BASE HOW TO
Used to configure tomcat with basic authentication with these users.įollowing example code shows how to change the default HTTP/HTTPS ports.
JREBEL BASE PASSWORD
List of users with username, password and roles.
The AJP protocol handler class name to be used (defaults to .AjpProtocol). The HTTPS protocol handler class name to be used (defaults to 11.Http11Protocol). The HTTP protocol handler class name to be used (defaults to 11.Http11Protocol). The keystore file to use for SSL, if enabled (by default, a keystore will be When false, this taskīlocks until the Tomcat server is stopped (defaults to false). This task completes as soon as the server has started. Specifies whether the Tomcat server should run in the background. The URL context path under which the web application will be registeredĭetermines whether the HTTPS connector should be created (defaults to false). The key to pass to Tomcat when requesting it to stop (defaults to null). The TCP port which Tomcat should listen for admin requests on (defaults The TCP port which Tomcat should listen for AJP requests on (defaults to 8009). The TCP port which Tomcat should listen for HTTPS requests on (defaults The TCP port which Tomcat should listen for HTTP requests on (defaults to 8080). Tomcat plugin exposes the following properties through the extension named tomcat: Tomcat plugin uses the same layout as the War plugin. The JSP compiler and turns JSP pages into Java source using Jasper. The plugin pre-defines the following tasksĪ Tomcat instance and deploys the exploded web application to it.Ī Tomcat instance and deploys the WAR to it. Sure you don't mix up Tomcat libraries of different versions. The Tomcat runtime libraries need to be added to the configuration tomcat.Īt the moment the Tomcat versions 6.x and 7.x are supported by the plugin. Tomcat base plugin, include the following code snippet in your build script: apply plugin: '-base' The downside is thatĮach task has to be configured individually in your build script. Want to set up the container solely for functional testing. Tasks, you will want to use the -base plugin.
JREBEL BASE FULL
You need full control over your tasks or don't want to go with the preconfigured To use the Tomcat plugin, include theįollowing code snippet in your build script: apply plugin: '' If you are OK if the preconfigured tasks, this is the preferrable option. The plugin helps you get started quickly.
Tasks for starting and stopping an embedded Tomcat container and exposes Tomcat custom task types, pre-configures classpath. Classpath 'com.bmuschko:gradle-tomcat-plugin:2.2.4 '
0 kommentar(er)
