New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Jetty 11.x Branch #4568
Comments
Some dependencies we need to track. APIs from Jakarta EE 9 and implementations:
|
As an alternative, I'd like to consider making servlet-5.0 support an optional modules within jetty-10, so that it can support both servlet 4.0 and 5.0. It would do this initially by facading the 5.0 API to run directly on top of the Jetty request/response/context/etc. even though they are dependent on 4.0. The main issue will be how to support request/response wrapping as we currently depend on the 4.0 servlet-API in the handler signature. However, there are alternate mechanisms for this. |
I have created #4578 to discuss the alternative approach for supporting jarkata APIs within jetty-10. |
I see Jasper 10.0.0-M1 available on maven central now - https://search.maven.org/artifact/org.apache.tomcat/tomcat-jasper/10.0.0-M1/jar |
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
- Update the jetty-11.0.x branch to use Jakarta WebSocket API. - Rename websocket classes, variables and comments using javax to use jakarta instead. Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
- Update the jetty-11.0.x branch to use Jakarta WebSocket API. - Rename websocket classes, variables and comments using javax to use jakarta instead. Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
- Update the jetty-11.0.x branch to use Jakarta WebSocket API. - Rename websocket classes, variables and comments using javax to use jakarta instead. Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
- Update the jetty-11.0.x branch to use Jakarta WebSocket API. - Rename websocket classes, variables and comments using javax to use jakarta instead. Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
- Update the jetty-11.0.x branch to use Jakarta WebSocket API. - Rename websocket classes, variables and comments using javax to use jakarta instead. Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
- Update the jetty-11.0.x branch to use Jakarta WebSocket API. - Rename websocket classes, variables and comments using javax to use jakarta instead. Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
- Update the jetty-11.0.x branch to use Jakarta WebSocket API. - Rename websocket classes, variables and comments using javax to use jakarta instead. Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
- Update the jetty-11.0.x branch to use Jakarta WebSocket API. - Rename websocket classes, variables and comments using javax to use jakarta instead. Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
This has been completed a long time ago. |
We need to decide when to spin off the Jetty-11 branch, and then do so.
The text was updated successfully, but these errors were encountered: