-
Notifications
You must be signed in to change notification settings - Fork 221
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
Jakarta Servlet API 5.0+ #451
Comments
The discussion: #555 |
Instead of Jetty, we use now Undertow (core), which has fewer dependencies and doesn't depend on Servlet API at all. At the same time the version used for undertow-servlet library will use Servlet API 6 and still be JDK11 compatible. On the other hand, Jetty 12 is multi-servlet-API version, but requires JDK17.
…s/test-util HttpTestUtil.java was moved (for now) to server/core, but soon there will be Servlet API 4 and 6 specific versions of this class.
yikes. The problem with Spring support for Jolokia 2.0 is that while we want Servlet API 5+ ( |
…tty 11 now Some org.eclipse.jetty.http.UriCompliance adjustments were needed (to be documented soon).
Yes, Spring Boot 3 supports only Java 17+. I don't think it's a problem though; we can just support Java 11, 17, ... and Spring Boot can utilise Jolokia 2.0 with Java 17+. The only thing we need to do is just turn off the Spring Boot related subprojects for Java 11, as enabling them for Java 11 doesn't make sense. |
Sure - I'll add proper Maven profiles. |
Awesome! 🎉 |
The servlet API is moving to the jakarta namespace from javax.
https://jakarta.ee/specifications/servlet/5.0/
Would be great to get a release for the new namespace.
The text was updated successfully, but these errors were encountered: