Joakim Erdfelt

While the initial description of the issue isn't the same, the root cause, and the fix, seem to be the same. See PR * #11719

Probably a good idea to be extra strict on the response line. After all, what would happen if the HttpClient decided to connect to something that isn't HTTP? (eg: an...

> Jetty 12 is aligned with Jakarta EE 10, whereas Jetty 9 is aligned with Jakarta EE 8. > Jersey 3.1.x is aligned with Jakarta EE 10, whereas Jersey 2.x...

Using your definitions of Jersey versions to EE levels, the extended chart would look like ... Jetty version | Environment | EE Level | Servlet ver | Servlet namespace |...

Technically speaking, Jersey 2.x supports Eclipse Jetty 7, as that's the version that introduced support for Servlet 2.4 (Jetty 8 was Servlet 3.0)

@gpfeifer some history ... * Servlet 1.0 thru Servlet 3.1 were backward compatible. (meaning if you wrote for and older version and deployed on a newer version, no big deal,...

Those of us using codeql are getting warnings with `v4.4` (or older) versions of setup-maven (as codeql based builds are now enforcing node-16) And this new not-quite-a-version was a bit...

BTW, Jetty 12 was released. (with support for EE8 at `java.servlet`, EE9 at `jakarta.servlet`, and EE10 at `jakarta.servlet` at the same time) Jetty's own tests use PaxWeb for each of...

This issue has been open long enough that Jetty 10 and Jetty 11 are now at End of Community Support. * https://github.com/jetty/jetty.project/issues/10485 Jetty 12 is the only supported version of...