We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Spring Boot 3.2 just released and introduced support for Jetty 12. There were quite a few changes introduced in Jetty 12 that render this starter unusable with Spring Boot 3.2.x and the spring-boot-starter-jetty starter.
spring-boot-starter-jetty
I guess there's not much you could do right now as compatibility for Jetty 12 likely also requires changes to logback-access itself.
Would it make sense to release a new version that updates the parent to Spring Boot 3.2.0 and explicitly states incompatibility with Jetty?
The text was updated successfully, but these errors were encountered:
I recognized that the mentioned underlying issue of the logback library is already solved. Are there any plans to make the spring-boot-starter compatible with SB 3.2/Jetty 12 as well?
Sorry, something went wrong.
there's an open PR that adds jetty 12 support: #407
v4.2.0 has been released! 🎉 It will be available in the Maven Central repository soon.
akkinoc
Successfully merging a pull request may close this issue.
Describe the problem you'd like to have solved
Spring Boot 3.2 just released and introduced support for Jetty 12. There were quite a few changes introduced in Jetty 12 that render this starter unusable with Spring Boot 3.2.x and the
spring-boot-starter-jetty
starter.I guess there's not much you could do right now as compatibility for Jetty 12 likely also requires changes to logback-access itself.
Would it make sense to release a new version that updates the parent to Spring Boot 3.2.0 and explicitly states incompatibility with Jetty?
The text was updated successfully, but these errors were encountered: