The Jetty team is happy to announce the immediate availability of a new
release for the Eclipse Jetty 9.3.x branch.


Jetty 9.3.22 is a maintenance release and contains a number of bug fixes.
It is recommended that all users upgrade as soon as they are able. Changes
for this release are listed below.

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: http://central.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
   <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 learn more.

Best Regards,

The Jetty Development Team


*jetty-9.3.22.v20171030 - 30 October 2017*
 + 1213 Upgrade to ASM Version 6.0_ALPHA for JDK9
 + 1692 Annotation scanning should ignore `module-info.class` files
 + 1705 Rejected executions in QueuedThreadPool can lead to memory leaks
 + 1797 JEP 238 - Multi-Release JAR files break bytecode scanning
 + 1814 Move JavaVersion to jetty-util for future Java 9 support
requirements
 + 1901 Reimplement PathWatcher as scanner
 + 1912 AbstractConnector EndPoint leak for failed SSL connections
 + 1914 jetty client fails to parse response with RFC2045 conformant
Content-Type:
charset="utf-8"
 + 1928 Backport #1705 to jetty-9.3.x
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

Reply via email to