Jetty Logo
Version: 9.3.7.v20160115
Contact the core Jetty developers at

private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery

Chapter 2. Using Jetty Introduction

Table of Contents

Downloading Jetty
Running Jetty
Deploying Web Applications
Finding Jetty in Maven

You can use Jetty in many different ways, ranging from embedding Jetty in applications, launching it from different build systems, from different JVM-based languages, or as a standalone distribution. This guide covers the latter, a standalone distribution suitable for deploying web applications.

Downloading Jetty

Downloading the Jetty Distribution

The standalone Jetty distribution is available for download from the Eclipse Foundation:

It is available in both zip and gzip formats; download the one most appropriate for your system. Notice that there are a number of other files with extensions of .sha or .md5 which are checksum files. When you download and unpack the binary, it is extracted into a directory called jetty-distribution-VERSION. Put this directory in a convenient location. The rest of the instructions in this documentation refer to this location as either JETTY_HOME or as $(jetty.home).

Distribution Content

A quick rundown of the distribution's contents follows. The top-level directory contains:

Table 2.1. Contents

license-eplv10-aslv20.htmlLicense file for Jetty
README.txtUseful getting started information
VERSION.txtRelease information
bin/Utility shell scripts to help run Jetty on Unix systems
demo-base/A Jetty base directory to run a Jetty server with demonstration webapps
etc/Directory for Jetty XML configuration files
lib/All the JAR files necessary to run Jetty
logs/Directory for request logs
modules/Directory of module definitions
notice.htmlLicense information and exceptions
resources/Directory containing additional resources for classpath, activated via configuration
start.d/Directory of *.ini files containing arguments that are added to the effective command line (see start.ini)
start.iniFile containing the arguments that are added to the effective command line (modules, properties and XML configuration files)
start.jarJar that invokes Jetty (see also Running Jetty)
webapps/Directory containing webapps that run under the default configuration of Jetty

See an error or something missing? Contribute to this documentation at Github!(Generated: 2016-03-17)