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

You can enable a set of libraries and XML configuration files via
the newly introduced module
system.

All of the pre-built XML configuration files shipped in Jetty are
now parameterized with properties that you can specify in your
${jetty.base}/start.ini (demonstrated in Quick Start
Configuration).

There is no longer a

These are powerful new features, made to support a variety of styles
of configuring Jetty, from a simple property based configuration, to
handling multiple installations on a server, to customized stacks of
technology on top of Jetty, and even the classic, custom XML configurations
of old.

For example, if you use the ${jetty.base} concepts
properly, you can upgrade the Jetty distribution without having to remake
your entire tree of modifications to Jetty. Simply separate out your
specific modifications to the ${jetty.base}, and in the
future, just upgrade your ${jetty.home} directory with a
new Jetty distribution.

Executing start.jar

When you execute start.jar the system:

Loads and parses all INIs found in
${jetty.base}/start.d/*.ini as command line
arguments.

Loads and parses ${jetty.base}/start.ini as
command line arguments.

Parses actual command line arguments used to execute
start.jar itself.

Also lists enabled state based on information present on the
command line, and all active startup INI files.

--module=<name>,(<name>)*

Enables one or more modules by name (use --list-modules to see
the list of available modules).

This enables all transitive (dependent) modules from the
module system as well.

If you use this from the shell command line, it is considered
a temporary effect, useful for testing out a scenario. If you want
this module to always be enabled, add this command to your
${jetty.base}/start.ini.

--add-to-start=<name>,(<name>)*

Enables a module by appending lines to the
${jetty.base}/start.ini file.

The lines that are added are provided by the module-defined
INI templates.

Note: Transitive modules are also appended.

--add-to-startd=<name>,(<name>)*

Enables a module via creation of a module-specific INI file in
the ${jetty.base}/start.d/ directory.

The content of the new INI is provided by the module-defined
ini templates.

Note: Transitive modules are also created in the same
directory as their own INI files.

--write-module-graph=<filename>

Advanced feature: Creates a graphviz dot file
of the module graph as it exists for the active
${jetty.base}.

Note: The server must have been started with various stop
properties for this to work.

Properties:

STOP.PORT=<number>

The port to use to stop the running Jetty server. This
is an internal port, opened on localhost, used solely for
stopping the running Jetty server. Choose a port that you do
not use to serve web traffic.

Required for --stop to function.

STOP.KEY=<alphanumeric>

The passphrase defined to stop the server.

Required for --stop to function.

STOP.WAIT=<number>

The time (in seconds) to wait for confirmation that the
running Jetty server has stopped. If not specified, the
stopper waits indefinitely for the server to stop.

If the time specified elapses, without a confirmation of
server stop, then the --stop command exits with a non-zero
return code.