Version: 9.4.30.v20200611 |

What Version Do I Use?
Previous | Chapter 1. Introducing Jetty Home | Next

##### Contact the core Jetty developers at www.webtide.com

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 for sponsored feature development

## What Version Do I Use?

Jetty 9 is the most recent version of Jetty and has a great many improvements over previous versions. This documentation which focuses on Jetty 9. While many people continue to use older versions of Jetty, we generally recommend using Jetty 9 as it represents the version of Jetty that we will actively maintain and improve over the next few years.

> ### Important

> It is important that only stable releases are used in production environments. Versions that have been deprecated or are released as Milestones (M) or Release Candidates (RC) are not suitable for production as they may contain security flaws or incomplete/non-functioning feature sets.

Table 1.1. Jetty Versions

Version | Year | Home | Min JVM | Protocols | Servlet | JSP | Status
--- | --- | --- | --- | --- | --- | --- | ---
11 | 2020- | Eclipse | 11 (2) | HTTP/1.1 (RFC 7230), HTTP/2 (RFC 7540), WebSocket (RFC 6455, JSR 356), FastCGI, JakartaEE Namespace(1) | 4.0.2 | 2.3 | UNSTABLE / Alpha
10 | 2019- | Eclipse | 11 (2) | HTTP/1.1 (RFC 7230), HTTP/2 (RFC 7540), WebSocket (RFC 6455, JSR 356), FastCGI | 4.0.2 | 2.3 | UNSTABLE / Beta
9.4 | 2016- | Eclipse | 1.8 | HTTP/1.1 (RFC 7230), HTTP/2 (RFC 7540), WebSocket (RFC 6455, JSR 356), FastCGI | 3.1 | 2.3 | Stable
9.3 | 2015- | Eclipse | 1.8 (3) | HTTP/1.1 (RFC 7230), HTTP/2 (RFC 7540), WebSocket (RFC 6455, JSR 356), FastCGI | 3.1 | 2.3 | Deprecated
9.2 | 2014-2018 | Eclipse | 1.7 (3) | HTTP/1.1 RFC2616, javax.websocket, SPDY v3 | 3.1 | 2.3 | Deprecated / End of Life January 2018
9.1 | 2013-2014 | Eclipse | 1.7 (3) | HTTP/1.1 RFC2616 | 3.1 | 2.3 | Deprecated / End of Life May 2014
9.0 | 2013-2013 | Eclipse | 1.7 (3) | HTTP/1.1 RFC2616 | 3.1-beta | 2.3 | Deprecated / End of Life November 2013
8 | 2009-2014 | Eclipse/Codehaus | 1.6 (3) | HTTP/1.1 RFC2616, WebSocket RFC 6455, SPDY v3 | 3.0 | 2.2 | Deprecated / End of Life November 2014
7 | 2008-2014 | Eclipse/Codehaus | 1.5 | HTTP/1.1 RFC2616, WebSocket RFC 6455, SPDY v3 | 2.5 | 2.1 | Deprecated / End of Life November 2014
6 | 2006-2010 | Codehaus | 1.4-1.5 | HTTP/1.1 RFC2616 | 2.5 | 2.0 | Deprecated / End of Life November 2010
5 | 2003-2009 | Sourceforge | 1.2-1.5 | HTTP/1.1 RFC2616 | 2.4 | 2.0 | Antique
4 | 2001-2006 | Sourceforge | 1.2, J2ME | HTTP/1.1 RFC2616 | 2.3 | 1.2 | Ancient
3 | 1999-2002 | Sourceforge | 1.2 | HTTP/1.1 RFC2068 | 2.2 | 1.1 | Fossilized
2 | 1998-2000 | Mortbay | 1.1 | HTTP/1.0 RFC1945 | 2.1 | 1.0 | Legendary
1 | 1995-1998 | Mortbay | 1.0 | HTTP/1.0 RFC1945 | - | - | Mythical

1. Due to Oracle’s ownership of the "Java" trademark, usage of the javax.* namespace has been restricted and the jakarta.* namespace was adopted by the Eclipse Foundation.
2. JPMS module support is optional
3. JDK9 and newer is not supported if using MultiRelease JAR Files, or Bytecode / Annotation scanning.

Previous | Top | Next
Chapter 1. Introducing Jetty | Home | Jetty and Java EE Web Profile

See an error or something missing? Contribute to this documentation at Github!(Generated: 2020-06-11)