-
Notifications
You must be signed in to change notification settings - Fork 8
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
ch.qos.logback.access:tomcat has non-optional Tomcat dependencies #17
Comments
Also, it seems 10.0 reached EOL and not supported anymore:
|
Hi @jonatan-ivanov!
And I'm using spring-boot 3.4 ch.qos.logback.access.tomcat 2.0.3 Full logs |
@levente160396 I'm also on spring boot 3.4.0 and the following works for me (gradle)
|
Yep, I removed those dependencies. The other exception is coming when I start the app.
here is my logbackValve configuration
|
@levente160396 |
logback-access-tomcat/pom.xml now declares tomcat-catalina and tomcat-coyote in provided scope. See also commit b9f5dcf |
I'm migrating from
ch.qos.logback:logback-access
toch.qos.logback.access:tomcat
.Or from
to
It seems that
ch.qos.logback.access:tomcat:2.0.3
brings in Tomcat 10.0.x (tomcat-catalina
andtomcat-coyote
) as its compile time dependency so I end up with these on my classpath:The problem is that I'm using Tomcat 10.1.x instead with Spring Boot 3.3.x which not just brings in Tomcat 10.1.x but does not seem to be compatible with 10.0.x. Also, Tomcat was an optional dependency for
ch.qos.logback:logback-access:1.4.14
.Excluding Tomcat from
ch.qos.logback.access:tomcat
seems to resolve the issue and this might be the case withjakarta.servlet
too:Let me leave here the whole error message in case someone gets the same:
The text was updated successfully, but these errors were encountered: