Full name:
org.mortbay.jetty:maven-jetty-plugin:6.1.26RC0:run-exploded
Description:
This goal is used to assemble your webapp into an exploded war and automatically deploy it to Jetty.
Once invoked, the plugin can be configured to run continuously, scanning for changes in the pom.xml and to WEB-INF/web.xml, WEB-INF/classes or WEB-INF/lib and hot redeploy when a change is detected.
You may also specify the location of a jetty.xml file whose contents will be applied before any plugin configuration. This can be used, for example, to deploy a static webapp that is not part of your maven build.
There is a reference guide to the configuration parameters for this plugin, and more detailed information with examples in the Configuration Guide.
Attributes:
Name | Type | Since | Description |
---|---|---|---|
contextPath | String | - | The context path for the webapp. Defaults to the name of the
webapp's artifact. |
scanIntervalSeconds | int | - | The interval in seconds to scan the webapp for changes and restart
the context if necessary. Ignored if reload is enabled. Disabled by
default. Default value is: 0. |
tmpDirectory | File | - | The temporary directory to use for the webapp. Defaults to
target/jetty-tmp |
webApp | File | - | The location of the war file. |
Name | Type | Since | Description |
---|---|---|---|
connectors | Connector[] | - | List of connectors to use. If none are configured then we use a
single SelectChannelConnector at port 8080 |
daemon | boolean | - | Determines whether or not the server blocks when started. The default behavior (daemon = false) will cause the server to pause other processes while it continues to handle web requests. This is useful when starting the server with the intent to work with it interactively. Often, it is desirable to let the server start and continue running subsequent processes in an automated build environment. This can be facilitated by setting daemon to true. Default value is: false. |
jettyConfig | File | - | Location of a jetty xml configuration file whose contents will be
applied before any plugin configuration. Optional. |
overrideWebXml | File | - | A web.xml file to be applied AFTER the webapp's web.xml file.
Useful for applying different build profiles, eg test, production
etc. Optional. |
reload | String | - | reload can be set to either 'automatic' or 'manual' if 'manual'
then the context can be reloaded by a linefeed in the console if
'automatic' then traditional reloading on changed files is enabled. Default value is: automatic. |
requestLog | RequestLog | - | A RequestLog implementation to use for the webapp at runtime.
Optional. |
skip | boolean | - | If true, execution of the plugin is skipped. Default value is: false. |
stopKey | String | - | Key to provide when stopping jetty on executing java
-DSTOP.KEY=<stopKey> -DSTOP.PORT=<stopPort> -jar
start.jar --stop |
stopPort | int | - | Port to listen to stop jetty on executing
-DSTOP.PORT=<stopPort> -DSTOP.KEY=<stopKey> -jar
start.jar --stop |
systemProperties | SystemProperties | - | System properties to set before execution. Note that these
properties will NOT override System properties that have been set
on the command line or by the JVM. They WILL override System
properties that have been set via systemPropertiesFile. Optional. |
systemPropertiesFile | File | - | File containing system properties to be set before execution Note
that these properties will NOT override System properties that have
been set on the command line, by the JVM, or directly in the POM
via systemProperties. Optional. |
userRealms | UserRealm[] | - | List of security realms to set up. Optional. |
webAppConfig | Jetty6PluginWebAppContext | - | The "virtual" webapp created by the plugin |
webDefaultXml | File | - | A webdefault.xml file to use instead of the default for the webapp.
Optional. |
Determines whether or not the server blocks when started. The default behavior (daemon = false) will cause the server to pause other processes while it continues to handle web requests. This is useful when starting the server with the intent to work with it interactively.
Often, it is desirable to let the server start and continue running subsequent processes in an automated build environment. This can be facilitated by setting daemon to true.
skip:
If true, execution of the plugin is skipped.