|
This goal is used in-situ on a Maven project without first requiring that the project
is assembled into a war, saving time during the development cycle.
The plugin forks a parallel lifecycle to ensure that the "compile" phase has been completed before invoking Jetty. This means
that you do not need to explicity execute a "mvn compile" first. It also means that a "mvn clean jetty:run" will ensure that
a full fresh compile is done before invoking Jetty.
Once invoked, the plugin can be configured to run continuously, scanning for changes in the project and automatically performing a
hot redeploy when necessary. This allows the developer to concentrate on coding changes to the project using their IDE of choice and have those changes
immediately and transparently reflected in the running web container, eliminating development time that is wasted on rebuilding, reassembling and redeploying.
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 How-To.
author:
janb | 