The Jetty team is extremely excited to announce the immediate availability
of Jetty 10 and Jetty 11! Both Jetty 10 and 11 include a vast number of bug
fixes and improvements. A summary of the high-level changes can be found
below and in a blog post we have published
<https://webtide.com/jetty-10-and-11-have-arrived/>. A full list of changes
can be found in the VERSION.txt packaged with each release.


This release available on the Eclipse Jetty project download page or from
the Maven Central repository:

   -

   Eclipse: https://www.eclipse.org/jetty/download.html
   -

   Maven Central: https://repo1.maven.org/maven2/org/eclipse/jetty/


Documentation for this release can be found on the Eclipse Jetty project
site:

   -

   https://www.eclipse.org/jetty/documentation/


If you find any issues with this release, or if you want to suggest future
enhancements, please file an issue on the Jetty GitHub page:

   -

   https://github.com/eclipse/jetty.project/issues/new


Commercial production and development support for Jetty is offered through
Webtide (www.webtide.com). Please contact us <https://webtide.com/contact/>
for more information or email [email protected] to discuss your specific
needs.


Best Regards,

The Jetty Development Team

Eclipse Jetty 10.x Highlights

   - Jetty 10.x has a minimum Java requirement of Java 11.
   - Jetty 10.x modules are proper JPMS modules with module-info.class.
   - Jetty 10.x supports the following technology specs (from the Jakarta
   EE 8 effort):
      - javax.servlet - 4.0.1
      - javax.servlet.jsp - 2.2
      - javax.servlet.jsp.jstl - 1.2
      - javax.el - 3.0.0
      - javax.websocket - 1.1
   - Jetty 10.x will be the last major version of Jetty to support the
   javax.servlet namespace.
   Use Jetty 11.x for the updated jakarta.servlet namespace.

Important Changes

   - Classic jetty logging facade has been replaced with slf4j-api usage
   - There is no longer a jetty-distribution, use jetty-home with a proper
   ${jetty.base} instead.
   See: Operations Guide: Architecture
   
<https://www.eclipse.org/jetty/documentation/10.0.0/operations-guide/index.html#og-begin-arch>
      - New demo jetty-start module exists to replace the old demo-base
      functionality.
   - Remove jetty-all uber artifact
   - Managing Configuration within a WebAppContext has a new API.
   (They are now self ordering and do not require knowledge of Jetty
   internals to use successfully)
   - Complete WebSocket refactoring, those using the Jetty APIs or
   embedded-jetty will need to update their code.
      - Support for WebSocket over HTTP/2 (client and server)
   - Jetty HttpClient has been improved.
      - Supports dynamic protocol upgrade (http/2 and http/1.1).
   - Session management has been refactored as well.

Changelog

*Special thanks to the following Eclipse Jetty community members for
participating in this release: @dejpec
<https://github.com/dejpec>, @attiand <https://github.com/attiand>, @sullis
<https://github.com/sullis>, @grgrzybek
<https://github.com/grgrzybek>, @schnittstabil
<https://github.com/schnittstabil>, @dennyac <https://github.com/dennyac>*


Eclipse Jetty 11.x Highlights

   - Jetty 11.x has a minimum Java requirement of Java 11.
   - Jetty 11.x modules are proper JPMS modules with module-info.class.
   - Jetty 11.x supports the following technology specs (from the Jakarta
   EE 9 effort):
      - jakarta.servlet - 5.0.0
      - jakarta.servlet.jsp - 3.0.0
      - jakarta.servlet.jsp.jstl - 2.0.0
      - jakarta.el - 4.0.0
      - jakarta.websocket - 2.0.0
   - Jetty 11.x is the first major version of Jetty to support the
   jakarta.servlet namespace.
   Use Jetty 10.x for the older (now outdated) javax.servlet namespace.

Important Changes

   - Classic jetty logging facade has been replaced with slf4j-api usage
   - There is no longer a jetty-distribution, use jetty-home with a proper
   ${jetty.base} instead.
   See: Operations Guide: Architecture
   
<https://www.eclipse.org/jetty/documentation/10.0.0/operations-guide/index.html#og-begin-arch>
      - New demo jetty-start module exists to replace the old demo-base
      functionality.
   - Remove jetty-all uber artifact
   - Managing Configuration within a WebAppContext has a new API.
   (They are now self ordering and do not require knowledge of Jetty
   internals to use successfully)
   - Complete WebSocket refactoring, those using the Jetty APIs or
   embedded-jetty will need to update their code.
      - Support for WebSocket over HTTP/2 (client and server)
   - Jetty HttpClient has been improved.
      - Supports dynamic protocol upgrade (http/2 and http/1.1).
   - Session management has been refactored as well.
_______________________________________________
jetty-users mailing list
[email protected]
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/jetty-users

Reply via email to