Jetty has been upgraded to the latest release on 10.x

Jetty 10 to 11 has a major change in the Servlet API from Servlet 4.0 to Servlet 5.0.

This change has some impact on the existing JSPs, however one major blocker has been identified with the sitemesh component, which depends on javax.servlet. Even if this dependency is provided, it is unable to cast/map these components to the modern jakarta.servlet.

When looking for valid alternatives for sitemesh, none were identified which state they support Servlet 5.0/Jakarta namespace, with other alternatives such as being retired.

Jetty 10 is still supported and appears to continue to be for the near future. Jetty 12 will be Servlet API independent , so it may be worth delivering Jetty 10 and waiting until Jetty 12 is released in a Stable version, where we will likely be able to keep our existing Sitemap and servlet version.

However, Jetty 12 will have a minimum JVM requirement of 17, which is potentially a big jump from where we are now, so how long Jetty 10 will be supported is a consideration. The Jetty 10 & 11 announcement post () mentioned the following:

'Enter Jetty 11. Jetty 11 is identical to Jetty 10 except that the javax.* packages now conform to the new jakarta.* namespace. Jetty 10 and 11 will remain in lockstep with each other for releases, meaning all new features or bug fixes in one version will be available in the other.'

‘Jetty 10 will be supported for a number of years to come. We have no plans on releasing it only to drop support for it in 12-18 months.’

However this was back in December 2020 so how many years of support will matter in this case.

An incremental upgrade of Jetty is underway. In the git branch that is linked to by JIRA, an upgrade to Jetty 10 is in a ready-ish state. The plan is to upgrade to Jetty 11.

For background information I have just found this PR which appears to track the change to deprecate UTF-16 based URL encoding from Jetty.