About Jetty
20090410 at 13:57 J
etty is poised to replace Tomcat as HTTP server of choice for many.
For one, it will be used to implemented GWT Hosted mode in the next GWT release.
At the moment it’s being folded into the Eclipse project — this is the jetty about page on the main Eclipse site. It shows the historical names, migration paths, and levels of support for the various versions of Jetty.
Jetty
Jetty was the name initially given to the HTTP server component from Mort Bay. The name Jetty has now grown to encompass the suite of components which includes a HTTP server, HTTP client, javax.servlet container, the hightide application server and many other related components and utilities. Jetty is now the name of the encompassing projects at mortbay(v1-v4), sourceforge(v5), codehaus(v6-) and eclipse(v7-).Mort Bay
The Java HTTP server that became jetty was originally developed in 1995 by Greg Wilkins of Mort Bay Consulting as part of an issue tracking application. Versions 1.x through to 6.1.x of jetty were developed under org.mortbay packaging and Mort Bay still holds the major part of the copyright on the jetty code base. Mort Bay directly hosted the jetty project until version 3.x and was the prime sponsor of development until 6.x.Webtide
The role of Mort Bay in leading the development of Jetty was taken over in 2006 by Webtide LLC, an open source services company that employs many of the jetty contributors.Sourceforge
From 2000 to 2005, the jetty project was hosted at sourceforge.net where versions 3.x, 4.x and 5.x were produced.Codehaus
In 2005, the jetty project moved to the codehaus for its hosting services and open source community. In 2009, after the core components of Jetty moved to eclipse, the jetty @ codehaus project continues to provide integrations, extensions and packaging of jetty.Eclipse
In 2009, the Jetty project moved it’s core components to be a project of the Eclipse Foundation, in order to improved IP processes and broaden the licensing and community of the project.
Version Home Java HTTP Servlet JSP Status 8.x Eclipse,
Codehaus1.6 HTTP/1.1
RFC26163.0 2.1 Experimental 7.x Eclipse,
Codehaus1.5,
J2MEHTTP/1.1
RFC26162.5 2.1 Stabilizing 6.x Codehaus 1.4-1.5 HTTP/1.1
RFC26162.5 2.0 Stable 5.x Sourceforge 1.2-1.5 HTTP/1.1
RFC26162.4 2.0 Mature 4.x Sourceforge 1.2,
J2MEHTTP/1.1
RFC26162.3 1.2 Ancient 3.x Sourceforge 1.2 HTTP/1.1
RFC20682.2 1.1 Fossilized 2.x Mortbay 1.1 HTTP/1.0
RFC19452.1 1.0 Legendary 1.x Mortbay 1.0 HTTP/1.0
RFC1945Mythical
eclipse, http, jetty, web dev, web server 
