An implementation that respects the NCSA format is available as .NCSARequestLog. Optional An implementation of the .RequestLog request log interface.You could instead configure the login services in a jetty xml file and add its location to the parameter. If you use a realm in your web.xml you can specify a corresponding realm here. Optional A list of .LoginService implementations.Settings that you make here do not override any system properties already set on the command line, by the JVM, or in the POM via systemProperties. Optional A file containing System properties to set for the execution of the plugin.For more information, see Setting System Properties. Optional Allow you to configure System properties for the execution of the plugin.By default this is 0, which disables hot deployment scanning. Optional The pause in seconds between sweeps of the webapp to check for changes and automatically hot redeploy if any are detected.to deploy, or if you have other Jetty objects that cannot be configured from the plugin. You might use it if you have other webapps, handlers, etc. Optional The location of a jetty.xml file that will be applied in addition to any plugin configuration parameters.You could also instead configure the connectors in a standard file and put its location into the parameter. Alternatively, you can specify as many connectors as you like. You can change this default port number by using the system property jetty.port on the command line, for example, "mvn -Djetty.port=9999 jetty:run". If you don't specify any, an NIO .nio.SelectChannelConnector will be configured on port 8080. Optional A list of .Connector objects, which are the port listeners for Jetty.These configuration elements set up the Jetty environment in which your webapp executes. Here are the configuration elements that are common to all goals: To run the jetty-maven-plugin with a particular goal, use this command: You might need to insert goal-specific configuration to run it properly. Each goal is an action you can run to accomplish a specific task, or to work with a particular web application setup. The jetty-maven-plugin has a number of distinct Maven goals. You can terminate the plugin with a in the terminal window where it is running. While it runs, it periodically scans for changes to your project files, so if you save changes and recompile your class files, Jetty redeploys your webapp, and you can instantly test the changes you just made. This starts Jetty and serves up your project on Jetty continues to run until you stop it. Then, from the same directory as your root pom.xml, simply type: This makes the development cycle more productive by eliminating the build and deploy steps: you use your IDE to make changes to the project, and the running web container automatically picks them up, allowing you to test them straight away. The plugin can then periodically scan your project for changes and automatically redeploy the webapp if any are found. You can add it to any webapp project that is structured according to the usual Maven defaults. The Jetty Maven plugin is useful for rapid development and testing. 7.10 Using GZip Compression and Other Jetty Extensions.7.3 Stopping the plugin from Another Terminal Window.6.6 jetty:start : Starting jetty without first executing the build up to "test-compile" phase.6.5 jetty:run-forked : Running an unassembled webapp in a separate jvm.6.4 jetty:deploy-war : Running a pre-assembled war.6.3 jetty:run-exploded : Running an assembled webapp as an expanded WAR.6.2 jetty:run-war : Running an assembled webapp as a war.6.1.1 Configuring additional parameters.6.1 jetty:run : Running an unassembled webapp.Package de.popup.handler import import .AbstractHandler import .ExecutionEvent import .ExecutionException import .ISelection import .IStructuredSelection import .handlers.