Joakim Erdfelt

@olamy this needs the update you mentioned on June 23rd.

The `jetty-maven-plugin` (that we create) supports proper maven scopes to avoid these issues. The other `maven-jetty-plugin` projects out there, that you might be using, we cannot say how they do...

> The warn message is fine for me but it should be configurable, when I am sure there is no problem with the conflict. If the conflict is at the...

In short, Thread creation is *very* expensive and time consuming, so the ThreadPool is designed with that in mind.

HTTP/3 support in Jetty is currently experimental and is not ready for production. Now, with HTTP/2, we support [RFC8441: Bootstrapping WebSockets with HTTP/2](https://datatracker.ietf.org/doc/html/rfc8441), so using HTTP/2 for WebSocket should work...

> ``` > GET /chat HTTP/2 _or HTTP/3 (but I don't know how it looks like_ > Host: server.example.com > Upgrade: websocket > Connection: Upgrade > Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ== > Origin:...

> @lachlan-roberts @joakime When would Jetty support HTTP/2 (and/or 3 [I know 3 is "hardly RFC" yet]) WebSocket Bootstrapping? Will it be announced somewhere so I can keep track of...

Having an IT test project that currently is not able to show output, being configured to show output would be a great first start. It should be a war project...

This might be a good issue to make more generic and submit to https://github.com/eclipse-ee4j/servlet-api/ as well.

> As I remember developers of Jigsaw project worked about 10 years. 10 years! What for? Modularization? Jetty and the Servlet spec have been around longer, over 2x longer in...