Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
This howto covers how to start up Jetty as standalone, and links to pages which cover alternative methods of startup.
Using the Start.jar
The easiest way to start Jetty, is to use the start.jar that comes with the distribution.
java -jar start.jar
The default options may be specified in the start.ini file, or if that is not present, they are defined in the start.config file that is within the start.jar.
To see the command line options for start.jar and help text for start.jar use:
java -jar start.jar --help
For a full description of start.jar features see Jetty Start.jar Feature Guide.
More start.jar examples
To run jetty with all options enabled:
java -jar start.jar OPTIONS=All
To run with JSP support (if available)
java -jar start.jar OPTIONS=Server,jsp
To run with JMX support
java -jar start.jar OPTIONS=Server,jmx etc/jetty-jmx.xml etc/jetty.xml
To run with JSP & JMX support
java -jar start.jar OPTIONS=Server,jsp,jmx etc/jetty-jmx.xml etc/jetty.xml
Alternative Startup Techniques
Jetty can be configured and started as an embedded webapp server from within another Java program. See Embedding Jetty Tutoral for more details. Once you have a main that runs Jetty, it is very easy to run this from your IDE, debugger and/or profiler.
Jetty can be started up from within Eclipse using a variety of techniques; see How to Use Jetty with Eclipse IDE for details.
Jetty Maven Plugin
You can run jetty directly on your maven webapp project - without even needing to assemble it into a war - see The Jetty Maven Plugin for details.
Jetty Ant Plugin
You can run jetty directly on your ant webapp project - see The Jetty Ant Plugin for details.
You can run jetty from a single jar file on one or more webapps and contexts using the Jetty Runner Jar.