Skip to content

ganqing2017/jetty

Folders and files

NameName
Last commit message
Last commit date
Jul 17, 2012
Feb 25, 2015
May 15, 2017
Jan 19, 2017
Feb 2, 2017
May 1, 2017
May 22, 2017
May 31, 2017
Feb 2, 2017
May 22, 2017
May 9, 2017
May 17, 2017
Apr 6, 2017
May 18, 2017
May 22, 2017
May 30, 2017
Apr 5, 2017
May 11, 2017
May 11, 2017
Jan 19, 2017
May 30, 2017
May 31, 2017
Apr 6, 2017
May 17, 2017
Jan 19, 2017
May 16, 2017
May 2, 2017
Jan 19, 2017
Jan 19, 2017
May 11, 2017
Apr 6, 2017
Jan 19, 2017
May 11, 2017
May 31, 2017
Jan 27, 2017
May 31, 2017
Mar 9, 2017
May 11, 2017
May 1, 2017
May 2, 2017
May 30, 2017
May 31, 2017
May 11, 2017
May 3, 2017
Jan 19, 2017
May 12, 2017
May 12, 2017
Jan 19, 2017
May 31, 2017
May 31, 2017
May 31, 2017
May 22, 2017
Jul 8, 2016
Dec 27, 2016
May 12, 2017
Nov 4, 2013
Jul 23, 2015
May 4, 2016
Feb 6, 2017
May 12, 2017
Nov 16, 2016
Oct 18, 2012
Jan 19, 2017
Mar 1, 2017
May 1, 2017
Jun 6, 2016
May 12, 2017

Repository files navigation

Eclipse Jetty Canonical Repository

This is the canonical repository for the Jetty project, feel free to fork and contribute now!

Submitting a patch or pull request?

Make sure you have an Eclipse Contributor Agreement (ECA) on file.

Project description

Jetty is a lightweight highly scalable java based web server and servlet engine. Our goal is to support web protocols like HTTP, HTTP/2 and WebSocket in a high volume low latency way that provides maximum performance while retaining the ease of use and compatibility with years of servlet development. Jetty is a modern fully async web server that has a long history as a component oriented technology easily embedded into applications while still offering a solid traditional distribution for webapp deployment.

Documentation

Project documentation is available on the Jetty Eclipse website.

Building

To build, use:

  mvn clean install

The Jetty distribution will be built in jetty-distribution/target/distribution.

The first build may take a longer than expected as Maven downloads all the dependencies.

The build tests do a lot of stress testing, and on some machines it is necessary to set the file descriptor limit to greater than 2048 for the tests to all pass successfully.

It is possible to bypass tests by building with mvn -Dmaven.test.skip=true install but note that this will not produce some of the test jars that are leveraged in other places in the build.

Professional Services

Expert advice and production support are available through Webtide.com.